| 1 |
On 11/1/05, Kito <kito@g.o> wrote: |
| 2 |
> > (2) Regular users install the prefix-enabled base system into a prefix |
| 3 |
> > (and add $PREFIX/bin, $PREFIX/sbin, etc. to .bashrc) |
| 4 |
> |
| 5 |
> I was thinking either they just open a shell and `source ${PREFIX}/ |
| 6 |
> etc/profile` or they can set their default shell to ${PREFIX}/bin/ |
| 7 |
> {bash,csh,zsh,whatever} which will already have a sane env with the |
| 8 |
> prefixed paths. |
| 9 |
|
| 10 |
'source ${PREFIX}/etc/profile' <-- Good thinking. |
| 11 |
|
| 12 |
> > (3) 'emerge mypackage' uses the gentoo system in $PREFIX to build |
| 13 |
> > 'mypackage' and install in into |
| 14 |
> > $PREFIX/regular/gentoo/path/for/the/package |
| 15 |
> |
| 16 |
> Thats the idea ;) Keep in mind, binary packages are a must, so there |
| 17 |
> will be a default prefix that has to be used for both the stage |
| 18 |
> tarballs and the binpkgs. It will still be possible for a user to |
| 19 |
> bootstrap to a custom prefix, but I think that we shouldn't really |
| 20 |
> support anything other than the default. |
| 21 |
|
| 22 |
Sounds good to me. Those picky enough to want some different prefix |
| 23 |
could also play with symlinks. |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-osx@g.o mailing list |
Archives