Enrico Weigelt wrote: > * Rafael Fernández López <[EMAIL PROTECTED]> wrote: > >> To sum up, portage will look for updates not only in your world >> file, but on dependencies too. > > ah, so let's say i've installed package A (in world) which > required B. if I use --update w/o --deep, only A gets updated, > but not B. > > What happens when a newer version of A requires some newer > version of B than currently installed ? Is B updated automatically ? > > > cu
Slightly more thorough explanation: You do "emerge packageA" , which emerges packageA and its dependency packageB. PackageB also has dependencies PackageC and PackageD. "emerge --update world" will update PackageA and its direct dependency PackageB. Packages C+D would only be updated if PackageB absolutely required more recent versions then what is already installed, and specifies that in its ebuild. "emerge --update --deep world" will update all the packages (A,B,C,D). Doing a deep update will try to update all packages on the computer except those that meet both of the following: 1: The package is not in the world file, and.... 2: the package is not a dependency, direct or indirect, of a package in the world file. To see if any meet those, run "emerge -p --depclean", and if necessary, add them to the world file or remove them. PaulNM -- [email protected] mailing list
