| 1 |
On Fri, 21 Dec 2007 10:52:04 +0800 |
| 2 |
Zhang Le <r0bertz@g.o> wrote: |
| 3 |
> Ciaran McCreesh wrote: |
| 4 |
> > On Fri, 21 Dec 2007 03:14:12 +0100 |
| 5 |
> > Luca Barbato <lu_zero@g.o> wrote: |
| 6 |
> >> Ciaran McCreesh wrote: |
| 7 |
> >>> Ok. What's the EAPI for the following ebuild that's written in an |
| 8 |
> >>> EAPI that hasn't been published yet? And how would I extract it? |
| 9 |
> >>> |
| 10 |
> >>> # Copyright blah blah |
| 11 |
> >>> |
| 12 |
> >>> import vim-spell using language="en" |
| 13 |
> >> If isn't published it doesn't exist in the main tree... |
| 14 |
> > |
| 15 |
> > You miss my point. If a package manager encounters the above, how |
| 16 |
> > does it determine the EAPI? |
| 17 |
> |
| 18 |
> As long as there is an agreement between the PM and ebuild, you can |
| 19 |
> get what you want no matter how it is defined. |
| 20 |
|
| 21 |
So how does one get the EAPI in the above example? Bear in mind that |
| 22 |
package managers can only use what's been agreed upon at the time they |
| 23 |
were released, not what might be agreed upon later -- and yet they need |
| 24 |
to be able to extract the EAPI from anything agreed upon later. |
| 25 |
|
| 26 |
-- |
| 27 |
Ciaran McCreesh |
Archives