1 |
Sort of responding to/being inspired by haubi's comment on -dev about |
2 |
"inherit eapi 4", I wondered whether we should make a prefix.eclass. |
3 |
|
4 |
Currently we have eprefixify as function provided by Portage, and hence |
5 |
ebuilds that use eprefixify cannot be straight ported to gentoo-x86. |
6 |
Most notable are the eselect-* ebuilds that some gentoo-x86 devs like to |
7 |
give full Prefix support, but simply can't because eprefixify (which we |
8 |
would use) cannot be used in gentoo-x86. |
9 |
|
10 |
So, should we start an eclass with for now eprefixify in there, and for |
11 |
every ebuild where we use it, start inheriting prefix and nuke the |
12 |
function from Portage? Somehow I think this is a good idea. |
13 |
|
14 |
Since I like haubi's idea about inherit doing the magic for eapis, |
15 |
perhaps this can even solve the problem we have with our EAPI mungling |
16 |
(all our ebuilds just inherit eapi prefix to "tag" them) and all |
17 |
eclasses (it remains a hell of a job to keep it working), as well as |
18 |
having prefix ebuilds live happily next to non-prefix ones. But for |
19 |
that we really need Portage to be able to mask based on what's in the |
20 |
inherit line, e.g. the resolver needs to take it into account. |
21 |
|
22 |
|
23 |
-- |
24 |
Fabian Groffen |
25 |
Gentoo on a different level |