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