| 1 |
Am 25.01.2011 17:40, schrieb Peter Volkov: |
| 2 |
> В Втр, 25/01/2011 в 14:33 +0100, Thomas Sachau пишет: |
| 3 |
>> Do you have some more arguments for your request? Most new developers |
| 4 |
>> will have to know about all EAPi versions anyway since they join an |
| 5 |
>> existing team with existing ebuilds, which will mostly not use the |
| 6 |
>> newest EAPI. |
| 7 |
>> |
| 8 |
>> As an argument againt this: Noone forces you to keep older EAPI |
| 9 |
>> versions of the ebuilds you maintain, you can always bump them to the |
| 10 |
>> latest EAPI. But why do you want to force this on all developers? |
| 11 |
> |
| 12 |
> I think your first paragraph is actually the argument to use latest EAPI |
| 13 |
> whenever possible. Such policy provides us with the path to avoid |
| 14 |
> situation you described while insisting on keeping old EAPI's obviously |
| 15 |
> will force new developer to learn ancient knowledge. IOW, such policy |
| 16 |
> provides path to simplify work in team. |
| 17 |
> |
| 18 |
|
| 19 |
If you as a maintainer or the maintaining team want to migrate your ebuilds to the latest EAPI, this |
| 20 |
is your decision. But if i am fine with an older EAPI version in those ebuilds i do maintain, what |
| 21 |
is wrong with that? Why do you want to force others into migrating to a newer EAPI, if they dont |
| 22 |
want it for whatever reason (like no need or upgrade path)? |
| 23 |
|
| 24 |
The only "nice to have" situation is, when you take over an existing ebuild. If it already uses the |
| 25 |
latest EAPI, you dont have to migrate it. On one side, you wont be able to avoid the migration, |
| 26 |
since exactly those ebuilds, which need a new maintainer wont be touched, so also wont be using the |
| 27 |
latest EAPI. On the other side, we have docs, which show you the changes with each EAPI, so you can |
| 28 |
read it once, adjust the ebuild and forget it again. I see nothing gained in this situation either, |
| 29 |
so we are back to my question above. |
| 30 |
|
| 31 |
The (maybe inofficial) suggestion is already to use the latest EAPI in new ebuilds. This is ok for |
| 32 |
me, as long as it is a suggestion. The same goes for the migration of ebuilds to the latest EAPI. |
| 33 |
But i am against the idea to enforce this for either new or even existing ebuilds. I prefer to do |
| 34 |
other work than useless EAPI-migration without a real need/benefit for me or the users. |
| 35 |
|
| 36 |
-- |
| 37 |
Thomas Sachau |
| 38 |
|
| 39 |
Gentoo Linux Developer |
Archives