-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
You didn't get my point. The global idea was that I thought that Portage first checks ebuilds before installing any package, and as there was no ebuild, the package shouldn't get installed. I did not know that there was the ebuild in the package itself. Stephane Alan McKinnon wrote: > On Tuesday 17 October 2006 11:44, Stephane Pointu wrote: >> Hi all, I have a question about portage behaviour: >> >> I have a package built in a certain version in /usr/portage/package >> but this version is not in portage tree (no ebuild for it). If I do a >> "emerge -kuav world" it takes this package but if I do a "emerge -uav >> world" it does not. Is this a normal behaviour? Shouldn't portage >> first check if there is an ebuild for it before installing the >> package? > > No, it makes perfect sense. When you use the -k switch, portage is in a > position to find and use the prebuilt package, so it will. > > When you don't use the -k switch, it won't use /usr/portage/packages per > the man page, so there's no sense in even attemtping to look for that > package - as there is no ebuild for that version, it cannot possibly > build it > > Your last question doesn't make sense - how can portage check for an > ebuild that you earlier clearly said does not exist? > > alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFNMnbWWLMt96bzSoRAjLXAKCMyIind950O8x+r/zqJ3oj2cqXdgCgnenu ImG22gm7zhrCSTrk8BjVvos= =zu0Y -----END PGP SIGNATURE----- -- gentoo-user@gentoo.org mailing list
