Just a nice idea :-)
With >=eix-0.7.3 you can configure such things in /etc/eix-sync.conf. For example, you can add there !layman -s whatever See "eix -h" and "man eix" /etc/eix-sync.conf for details.
Typo: "eix-sync -h" (not "eix -h"). But the only serious description of /etc/eix-sync.conf is in the eix manpage anyway.
(In reply to comment #1) > With >=eix-0.7.3 you can configure such things in /etc/eix-sync.conf. > For example, you can add there > !layman -s whatever > See "eix -h" and "man eix" /etc/eix-sync.conf for details. > That looks interesting, but IMO it should be a built in function... simply put if (layman is in worldfile) then run layman -S after/before emerge --sync
No, I dislike such MS-like automatism: People use many different settings and upgrade methods with Gentoo. This concerns in particular overlays and their updates: How often, when, and how, overlays are updated and/or whether a previous version is saved first etc. depends highly on the user's taste and needs, and I do not think that it is a good idea to "suggest" some method (like layman) by making it the default in eix-sync. For example, many people want to change automatically the downloaded overlay after downloading (e.g. by deleting a certain package which does not work for them), which means that it is reasonable to restore the "original" overlay before calling layman (so that rsync will not fetch unnecessarily unchanged but later deleted packages) etc. Such things could not easily be realized if eix-sync would force an automatism. IMHO, the only way to include all such special cases (and in particular to let the user easily change the order) with a reasonable config is to allow a script-like config. Adding the line "!layman -S" to this config (if this is your preference) is easy enough. [Actually, I even dislike that any "default" is suggested at all by eix-sync: Namely the usage of gensync if you specify only a name or "*" and no special command. However, I left it in due to backward compatibility with earlier versions of eix-sync].
Sorry, we will not fix this. There is also support in portage for this. Just create the file /etc/portage/bin/post_sync and put something in there. With portage-utils installed you already have a file there that allows usage in /etc/portage/postsync.d/ We have considered to do this by default in layman but we do not want to depend on portage-utils, and the portage devs do not want to allow maintainers to enable something like this by default - and I agree with them. So sorry, please do this manually.
Haha. Funny to read this more than 3 years later, and know that now it’s actually really a built-in function. ^^
