[gentoo-portage-dev] layman attempts to read all overlay lists when synchronizing local overlay

[gentoo-portage-dev] layman attempts to read all overlay lists when synchronizing local overlay

[Amit Dor-Shifer]

Hi.

I'm attempting to synchronize an existing local overlay (layman -s 
myoverlay).
/etc/layman/config.cfg:overlays contains an unresolvable URL.
The overlay is synchronizes as-expected, yet layman also issues an error:

<QUOTE>
* Failed to update the overlay list from: 
http://SOME_UNRESOLVED_ADDR/packages/my_overlay_list.xml
* Error was:
* <urlopen error [Errno -2] Name or service not known>
* Failed to read a cached version of the overlay list from 
http://SOME_UNRESOLVED_ADDR/packages/my_overlay_list.xml. You probably 
did not download the file before. The corresponding entry in your 
layman.cfg file will be disregarded.
</QUOTE>

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.

using layman-1.2.3

Thanks,

Amit

[gentoo-portage-dev] Re: layman attempts to read all overlay lists when synchronizing local overlay

[Duncan]

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.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [gentoo-portage-dev] Re: layman attempts to read all overlay lists when synchronizing local overlay

[Amit Dor-Shifer]

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.
>
>