1 |
2012-05-22 01:01:04 Francesco Riosa napisał(a): |
2 |
> 2012/5/22 Mike Frysinger <vapier@g.o>: |
3 |
> > On Monday 21 May 2012 18:16:25 Markos Chandras wrote: |
4 |
> >> Excuse me but the way this change was handled is a bit depressing. |
5 |
> >> First, the ebuilds should have been fixed to inherit eutils and then |
6 |
> >> remove eutils from autotools. Now, a bunch of ebuilds are broken out |
7 |
> >> of nowhere. I don't believe this issue was that urgent in order to |
8 |
> >> justify the significant breakage of portage tree. |
9 |
> > |
10 |
> > you're assuming the breakage was intentional. i also wouldn't really describe |
11 |
> > it as "significant", but that's just quibbling over an insignificant aspect. |
12 |
> |
13 |
> It's intentional not to revert the change, it's significant because it |
14 |
> involve a number of significant packages like icu, vim and boost |
15 |
|
16 |
These packages are not involved: |
17 |
|
18 |
dev-libs/icu ebuilds do not inherit autotools.eclass. |
19 |
An older ebuild (icu-4.8.1.1-r1.ebuild) inherits eutils.eclass only through versionator.eclass. |
20 |
|
21 |
app-editors/vim ebuilds do not inherit autotools.eclass, and inherit vim.eclass, |
22 |
which inherits eutils.eclass. |
23 |
|
24 |
dev-libs/boost ebuilds do not inherit autotools.eclass, and inherit check-reqs.eclass, |
25 |
flag-o-matic.eclass and versionator.eclass, which inherit eutils.eclass. |
26 |
|
27 |
-- |
28 |
Arfrever Frehtes Taifersar Arahesis |