Sorry. Didn't notice nofetch.
10x for the prompt reply.
Amit
Duncan wrote:
Amit Dor-Shifer posted on Wed, 09 Sep 2009 10:54:50 +0300 as excerpted:
I'm wondering: why should layman attempt to access overlay lists when
synching? It can use overlays.xml, since the overlay is already
installed locally.
Umm, did you RTFM? Allow me to quote "the friendly manpage" =:^) :
-f, --fetch
Fetches the remote list of overlays. You will usually NOT need
to explicitly specify this option. The fetch operation will be
performed automatically once you run the sync, sync-all, or
list action. You can prevent this automatic fetching using the
--nofetch option.
and...
-n, --nofetch
Prevents layman from automatically fetching the remote lists
of overlays. The default behavior for layman is to update all
remote lists if you run the sync, list or fetch operation.
Overlay locations and descriptions may change from time to time,
and by deliberate and documented design decision, layman defaults
to syncing its configured lists whenever you list or sync overlays.
As the manpage makes clear in two different places, the user does
have the ability to change that behavior, if desired, by simply
adding the appropriate option to his invocation.
That said, if the behavior bothers you and you're not invoking layman
updates from a script such that a single command updates both portage and
layman (plus updates your esearch/eix/etc database), that you could
therefore simply add the option to, I'd suggest filing a bug asking for a
layman.cfg option, similar to the one already there for nocheck.
