Re: [gentoo-dev] Re: Re: Re: Re: RFC: Make 10.0 profiles EAPI-2 'compliant'

[Andrew D Kirch <trelane@trelane.net>]

Ciaran McCreesh wrote:
> On Thu, 20 Aug 2009 06:13:59 -0400
> Andrew D Kirch <trelane@trelane.net> wrote:
>   
>
> > I look forward to seeing Funtoo's creation of EAPI funtoo-2.
>   

Obviously you don't get it.  We aren't going to spend time writing this
sort of spurious and unnecessary specification documents.  The fact that
this is even conscionable would be hugely concerning except for the fact
that you are not a Gentoo dev.  Nor do you, as I have proven, have
standing to file such a bug as you are not on the council (even as an
alternate), and the SOLE option for packages violating PMS per the
council is a council vote to mask the package. 

I'm having a hard time reconciling the following:

"The warnings don't make it to the user. The warnings make sure
developers catch the problem and fix it."

And:

"Just do it unconditionally. We're talking the tree here, not user
configuration files, so enforcing QA can only be a good thing."
"Portage should instead warn or error when this happens to prevent
people from accidentally abusing this."

Also:

"No. It's in direct violation of PMS, and only accidentally works with
Portage until Portage is fixed."

And:

"Portage should instead warn or error when this happens to prevent
people from accidentally abusing this."


Portage is a tool used by users, repoman is a tool used by developers
for tree QA.  Considering the zeal with which you are pushing this
"accidentally works with Portage until Portage is fixed", I believe a
reasonable person is going to look at the b.g.o bug, and at the Paludis
bug and realize that you're more interested in process than innovation,
and that you simply don't care about throwing needless confusing
warnings at users (indeed a prima facia examination of Paludis would
seem to confirm this, and my concerns WRT Paludis and the development
methods are well known).  I think they'll also realize that throughout
this process you've been less than honest, and a huge impairment to the
work going on at Funtoo.

Would someone who has access please resolve the bug as WONTFIX?  Thanks.

Andrew D Kirch
Funtoo.org