1 |
On Wed, 2003-12-10 at 17:49, Aron Griffis wrote: |
2 |
> On a similar topic to the -fPIC question, I've realized today that |
3 |
> |
4 |
> if use alpha; then |
5 |
> epatch ${FILESDIR}/${P}-alpha.patch || die "epatch failed" |
6 |
> fi |
7 |
> |
8 |
> is really the wrong thing (and I'm not talking about the die part, which |
9 |
> I know is controversial). I'm talking about the conditional application |
10 |
> of the patch. |
11 |
> |
12 |
> I think this should really be: |
13 |
> |
14 |
> # Patch for 64-bit but apply everywhere |
15 |
> epatch ${FILESDIR}/${P}-alpha.patch || die "epatch failed" |
16 |
> |
17 |
Hi Aron, |
18 |
|
19 |
Here's my take on this (slightly off-topic). The way Azarah designed |
20 |
epatch to be used can be seen very specifically in the xfree tarballs. |
21 |
So, if we decide to implement a *STANDARD* gentoo naming scheme and |
22 |
locations for all our patches then it would like: |
23 |
|
24 |
xxx_arch_${P*}-description.patch |
25 |
|
26 |
xxx = number -- determines order in which it is applied |
27 |
${P*} can be either ${PN} if the patch applies well enough to all |
28 |
versions, ${P} if specifically for one, or ${PF} if it's just for this |
29 |
revision of the ebuild (though epatch doesn't know about that, so that's |
30 |
thorny I guess). |
31 |
|
32 |
However, I agree 384% with you about making patches that can be applied |
33 |
across all architectures without harming or otherwise affecting the |
34 |
non-this ones. |
35 |
|
36 |
Ciao, |
37 |
-- |
38 |
Seemant Kulleen |
39 |
Developer and Project Co-ordinator, |
40 |
Gentoo Linux http://dev.gentoo.org/~seemant |
41 |
|
42 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3458780E |
43 |
Key fingerprint = 23A9 7CB5 9BBB 4F8D 549B 6593 EDA2 65D8 3458 780E |