[gentoo-dev] Caching service dependencies...

[gentoo-dev] Caching service dependencies...

[Norberto Bensa]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 304 bytes --]

Hello,

there are at least FOUR ${SUBJECT} messages for every package emerged. Is this 
on purpose or it's a bug?

$ emerge -V
Portage 2.0.49-r13 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r1, 2.4.23)


Regards,
Norberto
-- 
 14:43:42 up 1 day, 10:52,  1 user,  load average: 2.29, 1.99, 1.39

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Caching service dependencies...

[Dhruba Bandopadhyay]

Norberto Bensa wrote:
> Hello,
> 
> there are at least FOUR ${SUBJECT} messages for every package emerged. Is this 
> on purpose or it's a bug?
> 
> $ emerge -V
> Portage 2.0.49-r13 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r1, 2.4.23)
> 
> 
> Regards,
> Norberto

 From </usr/share/doc/portage-2.0.49-r13/ChangeLog.gz> :

   19 Sep 2003; Nicholas Jones <carpaski@gentoo.org> portage.py: Unregister
   signal handling after receiving the signal and resend the signal we got.
* Run depscan during env-update. Migrated eclass stuff into it's own pickle.
   Code for moving /var/cache/edb/dep into a pickle for each category added
   disabled via hardcoded value presently. Removed some try blocks in favor
   of detecting the cause of an error first -- Hopefully gives a little speed
   up. Cache fixes and useful output added. A tbz2 moving bug where an error
   was printed about files the destination existing already is now fixed. The
   dircache is cleared on every unmerge now, to ensure the cache does not
* interfere. bzip2 is spawned with the quiet flag now. Update list is sorted
   for proper year/quarter order now. -arch isn't an invalid keywork anymore.
   Generic pickle reading and writing functions added.

In short, yes it was deliberate.  However, I find it incredibly strange that:

(1) depscan.sh was added into env-update
(2) env-update is now run four times on *every single emerge*
(3) env-update now takes even longer to run
(4) env-update is so verbose about these routine maintenance tasks i.e:

$ env-update
 >>> Regenerating /etc/ld.so.cache...
  * Caching service dependencies...                               [ ok ]

Although running depscan.sh through env-update resolves the problem of 
uncached dependencies printing errors during /etc/init.d/ activities, I 
believe that it should be made silent in its output since the output is 
always constant and that it should not be run so many times!

I have a script which performs `emerge -Duv world`, logs the output and then 
produces all messages at the end.  In the case of env-update messages I have 
had to: echo $OUTPUT | sed '/Caching service dependencies//d'.

Incidentally, the idea of quietening bzip2 output was a welcome one.

Any comments?


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Caching service dependencies...

[Tim Yamin]

Agreed, I really miss my old, simple, and fast Portage and this new 
depscan.sh code makes things visually irritating [it has to be silent 
unless there's an error!] not to mention a slower Portage as a result.

Dhruba Bandopadhyay wrote:
> Norberto Bensa wrote:
> 
>> Hello,
>>
>> there are at least FOUR ${SUBJECT} messages for every package emerged. 
>> Is this on purpose or it's a bug?
>>
>> $ emerge -V
>> Portage 2.0.49-r13 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r1, 2.4.23)
>>
>>
>> Regards,
>> Norberto
> 
> 
>  From </usr/share/doc/portage-2.0.49-r13/ChangeLog.gz> :
> 
>   19 Sep 2003; Nicholas Jones <carpaski@gentoo.org> portage.py: Unregister
>   signal handling after receiving the signal and resend the signal we got.
> * Run depscan during env-update. Migrated eclass stuff into it's own 
> pickle.
>   Code for moving /var/cache/edb/dep into a pickle for each category added
>   disabled via hardcoded value presently. Removed some try blocks in favor
>   of detecting the cause of an error first -- Hopefully gives a little 
> speed
>   up. Cache fixes and useful output added. A tbz2 moving bug where an error
>   was printed about files the destination existing already is now fixed. 
> The
>   dircache is cleared on every unmerge now, to ensure the cache does not
> * interfere. bzip2 is spawned with the quiet flag now. Update list is 
> sorted
>   for proper year/quarter order now. -arch isn't an invalid keywork 
> anymore.
>   Generic pickle reading and writing functions added.
> 
> In short, yes it was deliberate.  However, I find it incredibly strange 
> that:
> 
> (1) depscan.sh was added into env-update
> (2) env-update is now run four times on *every single emerge*
> (3) env-update now takes even longer to run
> (4) env-update is so verbose about these routine maintenance tasks i.e:
> 
> $ env-update
>  >>> Regenerating /etc/ld.so.cache...
>  * Caching service dependencies...                               [ ok ]
> 
> Although running depscan.sh through env-update resolves the problem of 
> uncached dependencies printing errors during /etc/init.d/ activities, I 
> believe that it should be made silent in its output since the output is 
> always constant and that it should not be run so many times!
> 
> I have a script which performs `emerge -Duv world`, logs the output and 
> then produces all messages at the end.  In the case of env-update 
> messages I have had to: echo $OUTPUT | sed '/Caching service 
> dependencies//d'.
> 
> Incidentally, the idea of quietening bzip2 output was a welcome one.
> 
> Any comments?
> 
> 
> -- 
> gentoo-dev@gentoo.org mailing list
> 



--
gentoo-dev@gentoo.org mailing list