> Could you elaborate what the reasons FOR it are (not that I don't know > any, but you brought it up) since this will add work for every developer > to check a) how the behavior of the new EAPI impacts the current ebuild > and b) how the behvaior of inherited eclasses change depending on EAPI.
My main arguement is a modern code base, my intention is not to touch the ebuild if there is no reason. But if you are doing a version bump, bug fix etc you working on the package anyway. a) thats normal developer work b) if there is a bug in the eclass for a specified EAPI you should file a bug -- Johannes Huber (johu) Gentoo Linux Developer / KDE Team GPG Key ID F3CFD2BD
