В Втр, 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. -- Peter.
