On Fri, 2007-08-03 at 15:06 -0700, Chris Gianelloni wrote: > More and more, I am finding developers who are afraid to touch packages > for even minor things if they're not the maintainer. This is a sad > state of affairs and not the reason we have maintainers. We have > maintainers to assure that a package is being taken care of, not to > establish some kind of "territory" over that package. Because of this > misconception, I would like to come up with and document a listing of > things that any ebuild developer can feel free to do to any package > *without* maintainer consent. These are generally all minor things, but > things that I think are important. I'm going to list off the things > that I can think of, and encourage everyone else to speak up if I've > missed something.
Arch bugs that obviously don't affect other arches. An example of this is the pine/uw-imap/c-client stuff which does this make lnx Great! Make linux. Sucks for FreeBSD so I've been changing it to if use elibc_FreeBSD ; then make bsf else make lnx fi Obviously that's very simplified, but you get the idea. In this case I don't expect the ebuild maintainer to use Gentoo/FreeBSD. Thanks Roy -- [EMAIL PROTECTED] mailing list
