| 1 |
Ciaran McCreesh wrote: |
| 2 |
> On Fri, 21 Dec 2007 10:52:04 +0800 |
| 3 |
> Zhang Le <r0bertz@g.o> wrote: |
| 4 |
>> Ciaran McCreesh wrote: |
| 5 |
>>> On Fri, 21 Dec 2007 03:14:12 +0100 |
| 6 |
>>> Luca Barbato <lu_zero@g.o> wrote: |
| 7 |
>>>> Ciaran McCreesh wrote: |
| 8 |
>>>>> Ok. What's the EAPI for the following ebuild that's written in an |
| 9 |
>>>>> EAPI that hasn't been published yet? And how would I extract it? |
| 10 |
>>>>> |
| 11 |
>>>>> # Copyright blah blah |
| 12 |
>>>>> |
| 13 |
>>>>> import vim-spell using language="en" |
| 14 |
>>>> If isn't published it doesn't exist in the main tree... |
| 15 |
>>> You miss my point. If a package manager encounters the above, how |
| 16 |
>>> does it determine the EAPI? |
| 17 |
>> As long as there is an agreement between the PM and ebuild, you can |
| 18 |
>> get what you want no matter how it is defined. |
| 19 |
> |
| 20 |
> So how does one get the EAPI in the above example? |
| 21 |
|
| 22 |
That's the problem about the agreement between PM and ebuild. |
| 23 |
|
| 24 |
If this is agreed upon |
| 25 |
>>>>> import vim-spell using language="en" |
| 26 |
You should be able to get it. |
| 27 |
|
| 28 |
If not, then blame the ebuild writer. There is no problem with the agreement. |
| 29 |
|
| 30 |
> Bear in mind that |
| 31 |
> package managers can only use what's been agreed upon at the time they |
| 32 |
> were released, not what might be agreed upon later -- and yet they need |
| 33 |
> to be able to extract the EAPI from anything agreed upon later. |
| 34 |
|
| 35 |
Exactly my point. |
| 36 |
|
| 37 |
-- |
| 38 |
Zhang Le, Robert |
| 39 |
GPG key ID: 1E4E2973 |
| 40 |
Fingerprint: 0260 C902 B8F8 6506 6586 2B90 BC51 C808 1E4E 2973 |
| 41 |
-- |
| 42 |
gentoo-dev@g.o mailing list |
Archives