| 1 |
On Sun, 2004-07-18 at 16:23, Chris Frey wrote: |
| 2 |
> I looked briefly at the emerge build scripts, and it seems to me that it |
| 3 |
> would be fairly easy to incorporate the usage of stow inside the |
| 4 |
> portage system. |
| 5 |
|
| 6 |
Are you talking about this (http://www.gnu.org/software/stow/stow.html)? |
| 7 |
|
| 8 |
> econf() would need to be changed to read the --prefix directory from |
| 9 |
> a portage-stow configuration file, and tack on the name of the package |
| 10 |
> with version. |
| 11 |
> |
| 12 |
> install and uninstall would need to be changed to call stow and stow -D |
| 13 |
> if stow was in the USE flags. |
| 14 |
|
| 15 |
I agree with vapier that an eclass would be the best way to implement |
| 16 |
stow support. However, optional eclass inheritence makes DEPEND and IUSE |
| 17 |
dynamic, which, IIRC, is currently a big no-no. |
| 18 |
|
| 19 |
> This would allow people to maintain different versions of the same |
| 20 |
> application on their systems at the same time. Just stow/unstow at will |
| 21 |
> to switch. |
| 22 |
|
| 23 |
Isn't that the purpose of SLOTs? |
| 24 |
|
| 25 |
Cheers |
| 26 |
|
| 27 |
Andrew |
| 28 |
|
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-dev@g.o mailing list |
Archives