On 04/01/2017 22:25, Daniel Frey wrote: > On 01/04/2017 08:30 AM, Neil Bothwick wrote: >> On Wed, 4 Jan 2017 18:11:10 +0200, Alan McKinnon wrote: >> >>>> Using the --deep switch can / does pull in a lot of seemingly extra >>>> packages. >>> >>> --deep is practically *required* to do a full proper update. >>> >>> Say A is in world, and A depends on B which depends on C. >>> C is updated in the tree, and usually you will want C updated. >>> >>> However, update world will NOT update C. >>> Why? Because "world" is not a synonym for "everything", >>> "world" is something quite literal - the exact contents of >>> /var/lib/portage/world (and /var/lib/portage/world_sets if present) >> >>> "update world" updates that list only. >> >> That's not quite true, according to the man page. Without --deep portage >> considers only the specified files and their immediate dependencies >> (deps that are listed in the package's ebuild). So without --deep, >> updates to B as well a A would be picked up, but not C. >> >>> Adding --deep follows the >>> dependencies of the list, basically meaning >>> >>> "update --deep world" IS a synonym for "everything" >> >> > > I always do `emerge -uDN world`. Which is --update --deep --newuse... > I've just never had that happen with depclean before. Odd, no? > > I usually do: > > `emerge -uDN world` > > and > > `emerge -ac` to depclean afterwards. > > As I use --deep all the time, I'm still confused as to why needed > packages weren't installed. > > Dan >
s/I always do/I always do except this once when I forgot and then forgot that I forgot/g -- Alan McKinnon [email protected]
