begin quote On Wed, 28 Jan 2004 16:36:25 +0100 "Malte S. Stretz" <[EMAIL PROTECTED]> wrote:
> > > Just elimate the "u" from you command. U or u will apply in a global > > fashion. > > It actually seems to work, but now *I* am confused :) I've always used > -u, but must admit that I don't istall stuff from ~x86 very often. And > the manpage isn't very here. > > So what's the purpose of the --update switch, or better? Does it tell > emerge to recursively look at each and every dependecy and update it > if any newer version is available? as Ive come to understand it: -u searches for updates. if you have direct dependencies of a package. (foo needs bar >2.1 ) it will check for updates for all theese, and follow backwards. just doing "emerge foo" will only scan if you hit the "minimum required" dep, and be satisfied with that, even if it isn't the latest version avaiable. So, you have : foo-1.4 (latest is 2.3) bar-2.2 (latest is 2.4) and foo-2.3 depends on bar-2.1 or higher . this gives that : emerge foo : installs foo-2.3 emerge -u foo : installs foo-2.3 -and- bar-2.4 This also goes downwards, by checking each package foo, and bar depends on, and so on until you cant find more packages. > But if so, what if a package I want to update needs another one to be > upgraded. Is there any way (except stating the dependency explicitly > on the command line) to have that one upgraded, too, without standing > in front of a whole ~x86 system after it's finished? explicit dependencies will be dealt with "no matter what" . See previous paragraph for examples. still wondering? don't be too afraid to ask ;) //Spider -- begin .signature This is a .signature virus! Please copy me into your .signature! See Microsoft KB Article Q265230 for more information. end
pgp00000.pgp
Description: PGP signature
