1 |
On Fri, 6 May 2005 20:05:18 -0500 Brian Harring <ferringb@g.o> |
2 |
wrote: |
3 |
| On Fri, May 06, 2005 at 02:28:49PM +0100, Ciaran McCreesh wrote: |
4 |
| > The problem isn't the packages. The problem is the ebuilds. |
5 |
| Agreed, although seemed to take a bit of dancing to get done to the |
6 |
| fact that yes, changing the prefix has a good chance of working. |
7 |
| |
8 |
| From there, we're back to the old two step econf/eclasses _do_ address |
9 |
| a sizable portion of ebuilds in the tree ;) |
10 |
|
11 |
More to the point, they *don't* address a sizable portion of the ebuilds |
12 |
in the tree. |
13 |
|
14 |
| Not much for a keyword route personally, since (imo) it's a slight |
15 |
| perversion of the focus of keywords. If the keywording route was |
16 |
| taken, would need to either duplicate existing keywords (have |
17 |
| x86/~x86, and x86-weirdo-prefix ~x86-weirdo-prefix), or require two |
18 |
| specific keywords being set (x86 and weirdo-prefix from the example |
19 |
| above). |
20 |
| |
21 |
| I'd suspect your metadata addition (which needs a better name then |
22 |
| ICANINSTALLTO) is the best route. |
23 |
|
24 |
That was what I was proposing. Not KEYWORDS, a new variable. Which needs |
25 |
a better name than ICANINSTALLTO. |
26 |
|
27 |
| > | So, fink demonstration of --prefix hackery? |
28 |
| > |
29 |
| > If you want a better example, try either SGI or Sun's GNU tools |
30 |
| > ports. But they don't use ebuilds either. |
31 |
| Well, main point was that the underlying packages _can_ swing this |
32 |
| type of hackery for the most part, what is needed is a tweak to our |
33 |
| ebuild conventions to allow for it. |
34 |
|
35 |
'tweak' is too mild a term... As far as I can tell I'm the only person |
36 |
who's bothered to actually even try to look at this from an ebuild |
37 |
perspective -- not pretty... For every package in the tree that has a |
38 |
sed -e 's,/usr/local,/usr,g' there's another that would need a sed |
39 |
turning /usr into whatever prefix ends up as, and it's not at all |
40 |
obvious what they are. It gets even worse when you consider all the |
41 |
stuff with #!/usr/bin/blah hardcoded that will need changed to use our |
42 |
interpreter prefix -- these are very tricky to spot if you have a |
43 |
braindead vendor-supplied interpreter in /usr/bin too. |
44 |
|
45 |
Sure, it can be done, but not all at once, hence me screaming whitelist. |
46 |
|
47 |
| Meanwhile, iirc from the last irc conversation on this, either you or |
48 |
| dsd brought up the point of needing to be able to query if (using vim |
49 |
| as an example) vim-core was $home, rather then usr|$PREFIX. Care to |
50 |
| elaborate a bit? Mainly wondering if to encompass your requests, it |
51 |
| might require extra metadata from the depend standpoint. |
52 |
|
53 |
Ok, say we use ICANINSTALLTO (name!). Then if we have "prefix" as the |
54 |
destination, there's no problem, because we know that all our deps are |
55 |
installed in ${PREFIX} as well. However, if we're installing to "home", |
56 |
we need to know where our deps are -- for "home" installs I'm presuming |
57 |
we don't force a full dep tree in "home" (unlike for "prefix"). This |
58 |
*could* still be done with ${PREFIX} I guess? Or to avoid confusing |
59 |
things, ${DEPS_PREFIX}? Not really sure... |
60 |
|
61 |
-- |
62 |
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron) |
63 |
Mail : ciaranm at gentoo.org |
64 |
Web : http://dev.gentoo.org/~ciaranm |