Archives
Archives
| From: | Ciaran McCreesh <ciaran.mccreesh@×××××××××××××.uk> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Subject: | Re: EAPI definition Was: [gentoo-dev] [GLEP] Use EAPI-suffixed ebuilds (.ebuild-EAPI) | ||
| Date: | Fri, 28 Dec 2007 12:31:16 | ||
| Message-Id: | 20071228122810.1bbe2637@blueyonder.co.uk | ||
| In Reply to: | Re: EAPI definition Was: [gentoo-dev] [GLEP] Use EAPI-suffixed ebuilds (.ebuild-EAPI) by "Santiago M. Mola" |
||
| 1 | On Fri, 28 Dec 2007 13:25:13 +0100 |
| 2 | "Santiago M. Mola" <coldwind@g.o> wrote: |
| 3 | > On Dec 28, 2007 1:03 PM, Ciaran McCreesh |
| 4 | > <ciaran.mccreesh@×××××××××××××.uk> wrote: |
| 5 | > > There's no particular reason that new |
| 6 | > > version formats can't be introduced in a new EAPI so long as the |
| 7 | > > version strings don't appear in ebuilds using older EAPIs or in |
| 8 | > > profiles. Ditto for naming rules. |
| 9 | > |
| 10 | > Errr... so should we use new files in profiles for such new formats? |
| 11 | > (for example, p.masking an ebuild with a new version format). |
| 12 | |
| 13 | Possibly. Currently there's simply no way of doing it, nor of using |
| 14 | non-EAPI-0 features anywhere in profiles (you can't, for example, use |
| 15 | slot deps in package.mask). |
| 16 | |
| 17 | -- |
| 18 | Ciaran McCreesh |
| File name | MIME type |
|---|---|
| signature.asc | application/pgp-signature |
| Subject | Author |
|---|---|
| Re: EAPI definition Was: [gentoo-dev] [GLEP] Use EAPI-suffixed ebuilds (.ebuild-EAPI) | "Santiago M. Mola" <coldwind@g.o> |
| [gentoo-dev] Re: EAPI definition Was: [GLEP] Use EAPI-suffixed ebuilds (.ebuild-EAPI) | Duncan <1i5t5.duncan@×××.net> |