1 |
On 01-05-2011 17:04:18 +0400, Peter Volkov wrote: |
2 |
> В Вск, 01/05/2011 в 12:25 +0000, Fabian Groffen (grobian) пишет: |
3 |
> > grobian 11/05/01 12:25:59 |
4 |
> |
5 |
> > Fix econf call for Prefix: don't mix Prefix compatible and incompatible code |
6 |
> |
7 |
> > src_configure() { |
8 |
> > econf \ |
9 |
> > - --libdir=/$(get_libdir) |
10 |
> > + --libdir="${EPREFIX}"/$(get_libdir) |
11 |
> > } |
12 |
> |
13 |
> Could you clarify this bit, please? Should we use ED, EPREFIX, ... in |
14 |
> EAPI>=3 or we just ignore it and write ebuilds as always until prefix |
15 |
> team ports them and adds keywords? |
16 |
|
17 |
In short: yes, if you don't know what Prefix is, how it works or what |
18 |
exactly needs to be done, you can ignore it. |
19 |
You are always free to ask any team member in case you like to |
20 |
understand it and/or get it right. |
21 |
|
22 |
I added the ${EPREFIX} part to the econf call, because you do use ${ED} |
23 |
lateron in src_install() of the ebuild. |
24 |
|
25 |
The agreed "rules" are that an >=EAPI-3 ebuild does not have to support |
26 |
offset installs, but that such support can/may be added (by e.g. the |
27 |
Prefix team). |
28 |
|
29 |
In this case the ebuild was half/half, which causes needless bugs with |
30 |
confusing descriptions, and it caught my eye, so I just took the liberty |
31 |
to fix it, even though the ebuild does not report to be in use for any |
32 |
Prefix arch at the moment. |
33 |
|
34 |
|
35 |
-- |
36 |
Fabian Groffen |
37 |
Gentoo on a different level |