| 1 |
Fernando J. Pereda wrote: |
| 2 |
> On Tue, Dec 18, 2007 at 07:45:44PM +0000, Duncan wrote: |
| 3 |
>> "Fernando J. Pereda" <ferdy@g.o> posted |
| 4 |
>> 20071218175632.GC4423@××××××.org, excerpted below, on Tue, 18 Dec 2007 |
| 5 |
>> 18:56:32 +0100: |
| 6 |
>> |
| 7 |
>>>> And as we have now learned that EAPI strings are not limited to digits |
| 8 |
>>>> (see ciaranm's message) and may even contain blanks (see grobian's |
| 9 |
>>>> message), we would have ebuilds with very strange filenames. |
| 10 |
>>> What's the problem with this? |
| 11 |
>> 'app-shells/bash-3.2_p17-r1.ebuild-prefix 1' (note the space) anyone? |
| 12 |
> |
| 13 |
> I know what filenames with spaces mean, thank you very much. |
| 14 |
> |
| 15 |
>> How about when we have a dozen or so EAPIs active, several of which apply |
| 16 |
>> to a specific ebuild? |
| 17 |
>> |
| 18 |
>> 'app-shells/bash-3.2_p17-r1.ebuild-prefix 1 2 foo zork bar baz fa querty |
| 19 |
>> 3 8 4' (and that example uses no odd chars beyond the EAPI component |
| 20 |
>> space separator)? |
| 21 |
> |
| 22 |
> This is talking about something not covered by this GLEP.... so what is |
| 23 |
> your point? |
| 24 |
> |
| 25 |
|
| 26 |
I think the glep should try to address this concern... |
| 27 |
|
| 28 |
lu |
| 29 |
|
| 30 |
-- |
| 31 |
|
| 32 |
Luca Barbato |
| 33 |
Gentoo Council Member |
| 34 |
Gentoo/linux Gentoo/PPC |
| 35 |
http://dev.gentoo.org/~lu_zero |
| 36 |
|
| 37 |
-- |
| 38 |
gentoo-dev@g.o mailing list |
Archives