| 1 |
Ciaran McCreesh wrote: |
| 2 |
> On Fri, 21 Dec 2007 11:51:03 +0800 |
| 3 |
> Zhang Le <r0bertz@g.o> wrote: |
| 4 |
>> That's the problem about the agreement between PM and ebuild. |
| 5 |
>> |
| 6 |
>> If this is agreed upon |
| 7 |
>>>>>>> import vim-spell using language="en" |
| 8 |
>> You should be able to get it. |
| 9 |
>> |
| 10 |
>> If not, then blame the ebuild writer. There is no problem with the |
| 11 |
>> agreement. |
| 12 |
> |
| 13 |
> Uh... It's not agreed upon currently. |
| 14 |
|
| 15 |
It is not about whether it is agreed upon currently. |
| 16 |
As long as there is an agreement in any given point of time, it is OK. |
| 17 |
Such as, put your EAPI definition on the first line of your ebuild, like |
| 18 |
EAPI="value" |
| 19 |
|
| 20 |
>>> Bear in mind that |
| 21 |
>>> package managers can only use what's been agreed upon at the time |
| 22 |
>>> they were released, not what might be agreed upon later -- and yet |
| 23 |
>>> they need to be able to extract the EAPI from anything agreed upon |
| 24 |
>>> later. |
| 25 |
>> Exactly my point. |
| 26 |
> |
| 27 |
> So we all agree that suffixes are the solution, since they solve this |
| 28 |
> problem and in-ebuild-content restrictions don't. Good. |
| 29 |
|
| 30 |
No, quite contrary. |
| 31 |
See above. |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Zhang Le, Robert |
| 36 |
GPG key ID: 1E4E2973 |
| 37 |
Fingerprint: 0260 C902 B8F8 6506 6586 2B90 BC51 C808 1E4E 2973 |
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives