| 1 |
>>>>> On Thu, 16 Mar 2017, Alexis Ballier wrote: |
| 2 |
|
| 3 |
> Indeed, but that eclass fails to follow devmanual eclass 101 [1]: |
| 4 |
> An eclass is a collection of code which can be used by more than one |
| 5 |
> ebuild. |
| 6 |
|
| 7 |
Which is the case here: |
| 8 |
|
| 9 |
sys-devel/autoconf/autoconf-2.13.ebuild | 10 +--- |
| 10 |
sys-devel/autoconf/autoconf-2.59-r7.ebuild | 11 +--- |
| 11 |
sys-devel/autoconf/autoconf-2.61-r2.ebuild | 11 +--- |
| 12 |
sys-devel/autoconf/autoconf-2.62-r1.ebuild | 11 +--- |
| 13 |
sys-devel/autoconf/autoconf-2.63-r1.ebuild | 11 +--- |
| 14 |
sys-devel/autoconf/autoconf-2.64.ebuild | 11 +--- |
| 15 |
sys-devel/autoconf/autoconf-2.65-r1.ebuild | 11 +--- |
| 16 |
sys-devel/autoconf/autoconf-2.67.ebuild | 11 +--- |
| 17 |
sys-devel/autoconf/autoconf-2.68.ebuild | 11 +--- |
| 18 |
sys-devel/autoconf/autoconf-2.69-r2.ebuild | 11 +--- |
| 19 |
sys-devel/autoconf/autoconf-9999.ebuild | 15 ++--- |
| 20 |
|
| 21 |
> While this eclass might be a good temporary solution, I find it a |
| 22 |
> rather convincing argument for per-package eclasses :) |
| 23 |
|
| 24 |
Yes, if there was sufficient demand for such a feature, and it would |
| 25 |
therefore reduce the number of global eclasses significantly. IMHO it |
| 26 |
wouldn't be worth it for only a handful of packages. |
| 27 |
|
| 28 |
Ulrich |
| 29 |
|
| 30 |
> [1] https://devmanual.gentoo.org/eclass-writing/index.html |
Archives