| 1 |
On Jul 6, 2005, at 8:01 PM, Nathan L. Adams wrote: |
| 2 |
|
| 3 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 4 |
> Hash: SHA1 |
| 5 |
> |
| 6 |
> Sven Wegener wrote: |
| 7 |
> |
| 8 |
>> On Wed, Jul 06, 2005 at 08:41:43PM -0400, Mike Frysinger wrote: |
| 9 |
>> |
| 10 |
>> |
| 11 |
>>> On Wednesday 06 July 2005 08:20 pm, Sven Wegener wrote: |
| 12 |
>>> |
| 13 |
>>> |
| 14 |
>>>> We would like to introduce a new ebuild variable named |
| 15 |
>>>> EBUILD_FORMAT, |
| 16 |
>>>> |
| 17 |
>>> |
| 18 |
>>> seems like the name is much longer than it needs to be ... what's |
| 19 |
>>> wrong with |
| 20 |
>>> say 'EVER' ? |
| 21 |
>>> |
| 22 |
>> |
| 23 |
>> |
| 24 |
>> It's fine too. EBUILD_FORMAT was just the name that fell in |
| 25 |
>> #gentoo-portage once we discussed about it. |
| 26 |
>> |
| 27 |
>> Sven |
| 28 |
>> |
| 29 |
>> |
| 30 |
> |
| 31 |
> EVER looks like the english word 'ever'; what does it stand for? |
| 32 |
> EBUILD |
| 33 |
> VERSION? If so, how about EVERSION? Since when was variable name |
| 34 |
> length |
| 35 |
> a problem? Go with whatever best describes the variable and is easy to |
| 36 |
> figure out. |
| 37 |
|
| 38 |
Why not follow that logic through and use something like EBUILD_API ? |
| 39 |
the term VERSION implies release version which of course may not be |
| 40 |
tied to API changes... |
| 41 |
|
| 42 |
Kito |
| 43 |
|
| 44 |
> |
| 45 |
> Nathan |
| 46 |
> |
| 47 |
> |
| 48 |
> -----BEGIN PGP SIGNATURE----- |
| 49 |
> Version: GnuPG v1.4.1 (GNU/Linux) |
| 50 |
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org |
| 51 |
> |
| 52 |
> iD8DBQFCzH772QTTR4CNEQARAlimAJ0Yh80KpXqc0yZv6Gli+KqpWaKBxQCfU6pR |
| 53 |
> 2WqrKs4MfY+RCgpoFxZKD8Q= |
| 54 |
> =5nzV |
| 55 |
> -----END PGP SIGNATURE----- |
| 56 |
> -- |
| 57 |
> gentoo-dev@g.o mailing list |
| 58 |
> |
| 59 |
> |
| 60 |
|
| 61 |
-- |
| 62 |
gentoo-dev@g.o mailing list |
Archives