| 1 |
On Tuesday 16 April 2002 21:49, Adam Voigt wrote: |
| 2 |
> Well I was thinking of making the original prefix the default, so |
| 3 |
> essentially if PREFIX is set then like where the default path would |
| 4 |
> be /var then the new path would be PREFIX/var, but if PREFIX is |
| 5 |
> empty, then it just goes to /var. I was debating whether like man |
| 6 |
> pages should still go to the default directory, because as much |
| 7 |
> sense as it makes to make them go the default man directory, the |
| 8 |
> ./configure doesn't pay attention to where man pages are supposed |
| 9 |
> to go, it says "alright, I hope you know what your doing" and puts |
| 10 |
> everything, under your PREFIX, so that would be an absolute control |
| 11 |
> type deal, but having it set them in the default man page dir would |
| 12 |
> be more helpful in 99% of cases, so it's kind of a tossup. |
| 13 |
> |
| 14 |
|
| 15 |
Maybe I was thinking too much about binary packages. You are right, |
| 16 |
for ebuilds (disable prefixing on binary packages) prefixes can be |
| 17 |
compiled in not breaking packages. Packages that support prefix can |
| 18 |
use it in their config scripts, others (such as glibc) don't. |
| 19 |
|
| 20 |
Paul |
| 21 |
|
| 22 |
-- |
| 23 |
Paul de Vrieze |
| 24 |
Junior Researcher |
| 25 |
Mail: pauldv@××××××.nl |
| 26 |
Homepage: http://www.devrieze.net |
Archives