1 |
On Monday 21 May 2012 15:04:44 Pacho Ramos wrote: |
2 |
> El lun, 21-05-2012 a las 13:46 -0400, Alexandre Rostovtsev escribió: |
3 |
> > On May 20, autools.eclass was changed to no longer inherit eutils, see |
4 |
> > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/autotools. |
5 |
> > eclass?r1=1.133&r2=1.134 |
6 |
> > |
7 |
> > Relying on autotools.eclass for your eutils needs was always a terrible |
8 |
> > idea, but a few ebuilds did it anyway. Those ebuilds are now *broken* |
9 |
> > since they can no longer use epatch. See bug #416847 for an example. |
10 |
> > |
11 |
> > Check your ebuilds to make sure you inherit eutils in anything that uses |
12 |
> > epatch! |
13 |
> |
14 |
> Looks like ebuilds not inheriting eutils directly even using epatch are |
15 |
> a lot as I have seen running: |
16 |
> grep inherit $(grep -r epatch */*/*.ebuild| cut -d: -f1) | grep -v |
17 |
> eutils |
18 |
|
19 |
this is what i was using: |
20 |
find /usr/portage/*-* -name '*.ebuild' -exec grep -l '\<epatch\>' {} + | \ |
21 |
xargs grep -L inherit.*eutils |
22 |
|
23 |
there's quite a number there :( |
24 |
|
25 |
> Maybe they should be checked and a repoman warning should be added when |
26 |
> an ebuild is using epatch without inheriting eutils directly, otherwise |
27 |
> this problem could reappear if some other eclass no longer inherit it in |
28 |
> the future :-/ |
29 |
|
30 |
yeah, a repoman check would be a really good idea |
31 |
-mike |