On Mon, 2006-03-06 at 09:21 +0100, Kevin F. Quinn (Gentoo) wrote: > On Sun, 5 Mar 2006 20:46:25 -0500 > Mike Frysinger <[EMAIL PROTECTED]> wrote: > > > On Sunday 05 March 2006 19:48, Kevin F. Quinn (Gentoo) wrote: > > > This could be done via the profiles, perhaps - package.qa, something > > > like package.mask/use/keywords: > > > > i hate such things ... imo this information should stay in the ebuild > > and nowhere else ... > > I was thinking that the data would be "owned" by the QA team rather > than the package maintainers. I appreciate your pov, however.
That is a good point. Sadly I'd say I do not trust a large portion of our maintainers to do the right thing and not abuse the variable in the long run simply because they do not know how to fix a pkg properly. vs say exporting env variables all over the place (bloating ebuilds even more) a single file does offer quite a few advantages. In addition a single file could be directly parsed by the scanelf util and be simply told to ignore the additional QA checks using fnmatch() for paths or so. It would also provide an easy overview of whats messed up in the tree. shrug... [snip] > Heh - here's another idea for you to hate: > > QA_OVERRIDE="EXECSTACK=... > x86? ( TEXTRELS=... )" /me hates that also. -- Ned Ludd <[EMAIL PROTECTED]> Gentoo Linux -- gentoo-portage-dev@gentoo.org mailing list
