On Fri, 21 Dec 2007 10:52:04 +0800 Zhang Le <[EMAIL PROTECTED]> wrote: > Ciaran McCreesh wrote: > > On Fri, 21 Dec 2007 03:14:12 +0100 > > Luca Barbato <[EMAIL PROTECTED]> wrote: > >> Ciaran McCreesh wrote: > >>> Ok. What's the EAPI for the following ebuild that's written in an > >>> EAPI that hasn't been published yet? And how would I extract it? > >>> > >>> # Copyright blah blah > >>> > >>> import vim-spell using language="en" > >> If isn't published it doesn't exist in the main tree... > > > > You miss my point. If a package manager encounters the above, how > > does it determine the EAPI? > > As long as there is an agreement between the PM and ebuild, you can > get what you want no matter how it is defined.
So how does one get the EAPI in the above example? Bear in mind that package managers can only use what's been agreed upon at the time they were released, not what might be agreed upon later -- and yet they need to be able to extract the EAPI from anything agreed upon later. -- Ciaran McCreesh
signature.asc
Description: PGP signature
