| 1 |
On Saturday 04 September 2004 02:59, Ioannis Aslanidis wrote: |
| 2 |
> Will there be an alternative to inject? Sometimes (due to hardware |
| 3 |
> issues) it is necessary to compile manually the sources. So after a |
| 4 |
> make install, a simple emerge inject would do the work... |
| 5 |
|
| 6 |
package.provided doesn't work quite the same as --inject. To reiterate what I |
| 7 |
said in an earlier email: |
| 8 |
|
| 9 |
* Portage will not attempt to upgrade provided packages |
| 10 |
* Portage will not attempt to reinstall provided packages as part of world |
| 11 |
|
| 12 |
And caveats: |
| 13 |
|
| 14 |
* If the version of a provided package does not satisfy all dependencies, |
| 15 |
portage will install a version from source that does satisfy them. |
| 16 |
* Specifying the package name to emerge will ignore package.provided. |
| 17 |
|
| 18 |
As for your above reason for using --inject, there's a better way to do it: |
| 19 |
|
| 20 |
ebuild /path/to/ebuild/within/portage/tree unpack |
| 21 |
cd /var/tmp/portage/packagename-version/work/packagename-version |
| 22 |
configure |
| 23 |
make |
| 24 |
whatever else you need to do to get it to compile |
| 25 |
touch ../../.compiled |
| 26 |
ebuild /path/to/ebuild/within/portage/tree merge |
| 27 |
|
| 28 |
Regards, |
| 29 |
Jason Stubbs |
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-dev@g.o mailing list |
Archives