rename */*::gentoo-haskell to */*::haskell

    With modern versions of Portage package manager, it is important for
    repositories to use consistent names in the repository list (which is
    used to create repos.conf before installing the repository) and the
    repository itself. Right now failure to do so results in verbose
    warnings, while in future it may result in major issues with Portage
    behavior and become banned.

I've decided to align against layman registry entry.

Users will have to update their
    /etc/portage/package.* entries to update
from
    */*::gentoo-haskell
to
    */*::haskell
Signed-off-by: Sergei Trofimovich <siarheit@google.com>

README.rst

@@ -15,20 +15,20 @@ likely need to keyword everything in it::
     # and the overlay configuration itself:
     layman -a haskell
     # and unmask unstable versions for your arch:
-    echo "*/*::gentoo-haskell ~$(portageq envvar ARCH)" >> /etc/portage/package.accept_keywords
+    echo "*/*::haskell ~$(portageq envvar ARCH)" >> /etc/portage/package.accept_keywords
 
 And here is the trick to speed up metadata resolution a bit.
 If you happen to use ``eix-sync`` for rsyncs you might
 like the following ``/etc/eix-sync.conf``::
 
     *
-    @egencache --jobs="$(($(nproc) + 1))" --repo=gentoo-haskell --update --update-use-local-desc
+    @egencache --jobs="$(($(nproc) + 1))" --repo=haskell --update --update-use-local-desc
 
 It basically means:
 
 - sync overlays in layman list before the main tree sync
 
-- generate metadata for gentoo-haskell repo after main
+- generate metadata for haskell repo after main
   tree sync is done, using N+1 cores
 
 Getting involved

profiles/repo_name

-gentoo-haskell
+haskell

sets.conf

-[gentoo-haskell sets]
+[haskell sets]
 class = portage.sets.files.StaticFileSet
 multiset = true
-directory = ${repository:gentoo-haskell}/metadata/sets
+directory = ${repository:haskell}/metadata/sets