| 1 |
On Fri, 21 Dec 2007 03:44:20 +0100 |
| 2 |
Luca Barbato <lu_zero@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 |
> |
| 19 |
> from : |
| 20 |
> |
| 21 |
> - a default set by the repository, if we chose to use that |
| 22 |
> - a default set by itself |
| 23 |
> - by not understanding it thus failing in a brutal (hard error) or |
| 24 |
> gentle (ignore the file, warn) way. |
| 25 |
|
| 26 |
None of those solve the original problem. |
| 27 |
|
| 28 |
> I'm looking for alternatives. |
| 29 |
|
| 30 |
From the filename suffix. Simple! |
| 31 |
|
| 32 |
-- |
| 33 |
Ciaran McCreesh |
Archives