Re: [gentoo-user] emerge --update - why doesn't it update my kde packages

[KH <gentoo-user@konstantinhansen.de>]

Am 04.05.2010 12:17, schrieb Bert Swart:
> On Tue, May 04, 2010 at 12:09:25PM +0200, Helmut Jarausch wrote:
>> On  4 May, Bert Swart wrote:
>>> On Tue, May 04, 2010 at 10:57:10AM +0200, Helmut Jarausch wrote:
>>>> Hi,
>>>> the following situation puzzles me a lot.
>>>>
>>>> My 'standard' way of updating is
>>>> emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree @system @world
>>>>
>>>> but it didn't update anything.
>>>>
>>>> Still, eix confirmed there were quite a lot of kde packages which have
>>>> newer versions, and indeed,
>>>> emerge -auv1 -j4 --keep-going  $(qlist -IC kde-base/)
>>>> upgraded 24 packages.
>>>>
>>>> Where does this discrepancy come from?
>>> Do you  have --with-bdep set in /etc/make.conf?
>>
>> No. Are you saying that
>> emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree  --with-bdeps y @system @world
>> would have updated my kde packages, as well?
> Probably. Sometimes, not all packages are included as dependency
> if they are not strictly required. If you do want them to be
> upgraded, add --with-bdeps to EMERGE_DEFAULT_OPTS in
> /etc/make.conf. Or, like you did, upgrade them manually...
> See also http://www.gentoo.org/proj/en/portage/doc/faq.xml

Those are packages only required during buildtime. You could unmerge 
them after upgrading without loosing a funktion. Adding --with-bdeps to 
EMERGE_DEFAULT_OPTS might only wast some time and energy. You can also 
run depclean --with-bdeps (yes/no or something like that) to savely 
remove them.
My point is: If glsa doesn't list one of those packages I don't touch them.

Regards
kh

>>
>> Thanks,
>> Helmut.
>>
>>
>>
>>
>> --
>> Helmut Jarausch
>>
>> Lehrstuhl fuer Numerische Mathematik
>> RWTH - Aachen University
>> D 52056 Aachen, Germany
>>
>
>