Gentoo Archives: gentoo-dev

From: Mike Frysinger <vapier@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] autotools.eclass no longer inherits eutils; check your ebuilds!
Date: Mon, 21 May 2012 23:37:03
Message-Id: 201205211937.14732.vapier@gentoo.org
In Reply to: Re: [gentoo-dev] autotools.eclass no longer inherits eutils; check your ebuilds! by Francesco Riosa
1 On Monday 21 May 2012 19:24:27 Francesco Riosa wrote:
2 > 2012/5/22 Mike Frysinger:
3 > > On Monday 21 May 2012 19:01:04 Francesco Riosa wrote:
4 > >> 2012/5/22 Mike Frysinger:
5 > >> > On Monday 21 May 2012 18:16:25 Markos Chandras wrote:
6 > >> >> Excuse me but the way this change was handled is a bit depressing.
7 > >> >> First, the ebuilds should have been fixed to inherit eutils and then
8 > >> >> remove eutils from autotools. Now, a bunch of ebuilds are broken out
9 > >> >> of nowhere. I don't believe this issue was that urgent in order to
10 > >> >> justify the significant breakage of portage tree.
11 > >> >
12 > >> > you're assuming the breakage was intentional. i also wouldn't really
13 > >> > describe it as "significant", but that's just quibbling over an
14 > >> > insignificant aspect.
15 > >>
16 > >> It's intentional not to revert the change, it's significant because it
17 > >> involve a number of significant packages like icu, vim and boost, some
18 > >> of them already marked stable (from a fast grep from the one mentioned
19 > >> in the previous posts).
20 > >
21 > > you've identified the broke things. so fix them.
22 >
23 > wanna give me commit access for few hours?
24
25 just join as a dev and get it over with ;P
26
27 > I've already done mass changes to the tree when introducing
28 > virtual/mysql seem something doable the same way.
29
30 seems people have already fixed most (if not all) errors related to
31 autotools.eclass
32 -mike

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-dev] autotools.eclass no longer inherits eutils; check your ebuilds! Francesco Riosa <vivo75@×××××.com>