james wrote: > OK, > > So I just updated one of my system and all went fine. > > > I have not cleaned things up in a while, so I thought > I'd see what depclean says, know that I'm using kde4 > and sets..... > > > So I get a huge list, including lots of kde-base 4.2.2 packages. > > > Hmmm, something is not right. > 'emerge -uDNvp world' reveals nothing to update, yet depclean what > to remove lots of kde-base/<atom>-4.2.2 packages. Here's one example: > > > emerge -pv depclean shows this entry > <snip> > kde-base/libkdegames > selected: 4.2.2 > protected: none > omitted: none > > > OK eix shows this: > kde-base/libkdegames > Available versions: > (3.5) 3.5.9 ~3.5.10 > (4.2) (~)4.2.2 (~)4.2.3 > Installed versions: 4.2.2(4.2)(10:10:14 04/28/09) > > Now emerge what to update it: > > emerge -pv libkdegames > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild U ] kde-base/libkdegames-4.2.3 [4.2.2] > > > What am I missing here? Shouldn't the upgrade or world > pick up the the need to upgrade these packages, or > do I need some syntax to check my (kde 4) sets to see if > any of them need updating? (missed something here). > > > And why does depclean want to remove all of these kde 4 > packages? Surely, I do not have to put them > all in the world file? Use something other than depclean > with sets? > > > confused, > James > > > >
This may not be correct but here goes anyway. I don't think portage checks for sets that way. I may be wrong. If you want portage to check the sets for upgrades, you may need to add the name of the sets to the file /var/lib/portage/world_sets. I have @system in that file so that when I upgrade world, it checks system too. Someone else may have a better solution to this tho. Dale :-) :-)
