| 1 |
Amit Dor-Shifer posted on Wed, 09 Sep 2009 10:54:50 +0300 as excerpted: |
| 2 |
|
| 3 |
> I'm wondering: why should layman attempt to access overlay lists when |
| 4 |
> synching? It can use overlays.xml, since the overlay is already |
| 5 |
> installed locally. |
| 6 |
|
| 7 |
Umm, did you RTFM? Allow me to quote "the friendly manpage" =:^) : |
| 8 |
|
| 9 |
-f, --fetch |
| 10 |
Fetches the remote list of overlays. You will usually NOT need |
| 11 |
to explicitly specify this option. The fetch operation will be |
| 12 |
performed automatically once you run the sync, sync-all, or |
| 13 |
list action. You can prevent this automatic fetching using the |
| 14 |
--nofetch option. |
| 15 |
|
| 16 |
and... |
| 17 |
|
| 18 |
-n, --nofetch |
| 19 |
Prevents layman from automatically fetching the remote lists |
| 20 |
of overlays. The default behavior for layman is to update all |
| 21 |
remote lists if you run the sync, list or fetch operation. |
| 22 |
|
| 23 |
Overlay locations and descriptions may change from time to time, |
| 24 |
and by deliberate and documented design decision, layman defaults |
| 25 |
to syncing its configured lists whenever you list or sync overlays. |
| 26 |
As the manpage makes clear in two different places, the user does |
| 27 |
have the ability to change that behavior, if desired, by simply |
| 28 |
adding the appropriate option to his invocation. |
| 29 |
|
| 30 |
That said, if the behavior bothers you and you're not invoking layman |
| 31 |
updates from a script such that a single command updates both portage and |
| 32 |
layman (plus updates your esearch/eix/etc database), that you could |
| 33 |
therefore simply add the option to, I'd suggest filing a bug asking for a |
| 34 |
layman.cfg option, similar to the one already there for nocheck. |
| 35 |
|
| 36 |
-- |
| 37 |
Duncan - List replies preferred. No HTML msgs. |
| 38 |
"Every nonfree program has a lord, a master -- |
| 39 |
and if you use the program, he is your master." Richard Stallman |
Archives