Ciaran McCreesh wrote: > 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?
That's the problem about the agreement between PM and ebuild. If this is agreed upon >>>>> import vim-spell using language="en" You should be able to get it. If not, then blame the ebuild writer. There is no problem with the agreement. > 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. Exactly my point. -- Zhang Le, Robert GPG key ID: 1E4E2973 Fingerprint: 0260 C902 B8F8 6506 6586 2B90 BC51 C808 1E4E 2973 -- [EMAIL PROTECTED] mailing list
