Pacho Ramos schrieb: > I volunteer to do whatever conversions you want for every ebuild I find > if I have time... what prevents me from doing it is to commit that > changes to ebuilds not maintained by me and not knowing if developers > agree on using latest eapi if possible. A more general solution (or > policy) needs to be worked as, otherwise, tree won't be moved to latest > eapi ever because we would need to: > - Periodically send bugs + patches > - Ask for permission to commit > > And that for every eapi bump >
Either an ebuild has a responsive maintainer, which you can ask friendly to bump the EAPI because of feature X you would like to use or there is no maintainer, in which case you are free to touch/bump or last rite the ebuild. So i still dont see any need or requirement for a policy to force/require all devs to always use or switch to the latest avaidable EAPI. As already written in this thread, it would just mean less new ebuilds and less version bumps with such a policy. And i also prefer more work done with older EAPI versions around then less ebuilds/new versions with latest EAPI. -- Thomas Sachau Gentoo Linux Developer
signature.asc
Description: OpenPGP digital signature
