| 1 |
On 5/14/20 7:55 AM, Neil Bothwick wrote: |
| 2 |
> On Thu, 14 May 2020 18:17:06 +0800, Pengcheng Xu wrote: |
| 3 |
> |
| 4 |
>> That seems interesting. Do we need to include Portage install prefix |
| 5 |
>> (/var/tmp/portage/category/package/..., the image path prefix before |
| 6 |
>> actually merging with /)? |
| 7 |
>> |
| 8 |
>> Regards, |
| 9 |
> |
| 10 |
> No, just the --prefix=/home/blah/ that you want added to the ./configure |
| 11 |
> invocation. |
| 12 |
> |
| 13 |
|
| 14 |
This is a good way to install packages that you've built by hand into |
| 15 |
(say) your home directory, but it will cause problems if you try to |
| 16 |
trick portage into doing it. The big problem is that no other packages |
| 17 |
are going to know where to find the thing you just installed. Everything |
| 18 |
else in the Gentoo repository is designed to use standard values of |
| 19 |
PATH, LD_LIBRARY_PATH, the compiler's include dir, PKG_CONFIG_PATH, etc. |
| 20 |
If you take one program and put it somewhere non-standard, then every |
| 21 |
package depending on it is going to break. |
| 22 |
|
| 23 |
If you install an *additional* copy (built by hand) in your home |
| 24 |
directory, that's fine -- the system copy will still be in the right |
| 25 |
place -- you just don't want to hide the system copy where nobody can |
| 26 |
find it. |
Archives