| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi, |
| 5 |
|
| 6 |
You didn't get my point. The global idea was that I thought that Portage |
| 7 |
first checks ebuilds before installing any package, and as there was no |
| 8 |
ebuild, the package shouldn't get installed. I did not know that there |
| 9 |
was the ebuild in the package itself. |
| 10 |
|
| 11 |
Stephane |
| 12 |
|
| 13 |
Alan McKinnon wrote: |
| 14 |
> On Tuesday 17 October 2006 11:44, Stephane Pointu wrote: |
| 15 |
>> Hi all, I have a question about portage behaviour: |
| 16 |
>> |
| 17 |
>> I have a package built in a certain version in /usr/portage/package |
| 18 |
>> but this version is not in portage tree (no ebuild for it). If I do a |
| 19 |
>> "emerge -kuav world" it takes this package but if I do a "emerge -uav |
| 20 |
>> world" it does not. Is this a normal behaviour? Shouldn't portage |
| 21 |
>> first check if there is an ebuild for it before installing the |
| 22 |
>> package? |
| 23 |
> |
| 24 |
> No, it makes perfect sense. When you use the -k switch, portage is in a |
| 25 |
> position to find and use the prebuilt package, so it will. |
| 26 |
> |
| 27 |
> When you don't use the -k switch, it won't use /usr/portage/packages per |
| 28 |
> the man page, so there's no sense in even attemtping to look for that |
| 29 |
> package - as there is no ebuild for that version, it cannot possibly |
| 30 |
> build it |
| 31 |
> |
| 32 |
> Your last question doesn't make sense - how can portage check for an |
| 33 |
> ebuild that you earlier clearly said does not exist? |
| 34 |
> |
| 35 |
> alan |
| 36 |
-----BEGIN PGP SIGNATURE----- |
| 37 |
Version: GnuPG v1.4.2.2 (GNU/Linux) |
| 38 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 39 |
|
| 40 |
iD8DBQFFNMnbWWLMt96bzSoRAjLXAKCMyIind950O8x+r/zqJ3oj2cqXdgCgnenu |
| 41 |
ImG22gm7zhrCSTrk8BjVvos= |
| 42 |
=zu0Y |
| 43 |
-----END PGP SIGNATURE----- |
| 44 |
-- |
| 45 |
gentoo-user@g.o mailing list |
Archives