Archives
Archives
| From: | Marius Mauch <genone@g.o> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Subject: | Re: EAPI definition Was: [gentoo-dev] [GLEP] Use EAPI-suffixed ebuilds (.ebuild-EAPI) | ||
| Date: | Thu, 27 Dec 2007 19:17:36 | ||
| Message-Id: | 20071227201614.8bd1175a.genone@gentoo.org | ||
| In Reply to: | Re: EAPI definition Was: [gentoo-dev] [GLEP] Use EAPI-suffixed ebuilds (.ebuild-EAPI) by Luca Barbato |
||
| 1 | On Thu, 20 Dec 2007 08:10:13 +0100 |
| 2 | Luca Barbato <lu_zero@g.o> wrote: |
| 3 | |
| 4 | > Ok, that seems a fine definition of what an eapi is. Everybody agrees on it? |
| 5 | |
| 6 | Nope. EAPI (from my POV) defines the API that a package manager has to export to an ebuild/eclass. That includes syntax and semantics of exported and expected functions and variables (IOW the content of ebuilds/eclasses), but does not contain naming and versioning rules (as those impact cross-package relationships). |
| 7 | |
| 8 | Marius |
| 9 | -- |
| 10 | gentoo-dev@g.o mailing list |
| Subject | Author |
|---|---|
| Re: EAPI definition Was: [gentoo-dev] [GLEP] Use EAPI-suffixed ebuilds (.ebuild-EAPI) | Luca Barbato <lu_zero@g.o> |