Rich Freeman: > On Sat, Feb 7, 2015 at 10:06 AM, hasufell <hasuf...@gentoo.org> wrote: >> >> The council just chose the worst way, because it didn't want to upset >> either party involved in the discussion. >> > > The council simply upheld GLEP 39 - people don't HAVE to work with a > project team to work on packages. There is no QA policy that requires > any particular package to use any particular eclass, or install its > files in any particular directory. FHS compatibility is generally > encouraged, but even that has been trending differently in most > distros in recent years. > > Besides, I don't see two "parties" here. I see the games team which > for the most part doesn't say anything, and then I see a bunch of > individual maintainers who all have various preferences. > > The way we do games isn't going to change unless somebody steps up and > says "hey, I want to run the games team and take it in this > direction." You're more than welcome to do that. So far you haven't. > So, your repeated protests basically amount to complaining that > somebody else isn't doing work the way you'd prefer that they do it. > You've made that loud and clear. Now all you need to do is find > somebody who actually wants to do the work for you. > > Don't get me wrong - I don't mind when people point out inconsistency. > It is just that when all you do is point it out repeatedly without > actually personally doing anything to help change things, it gets a > bit old. That is why the Council tends to choose the path of minimal > interference. We don't really have the ability to force people to > work on things. >
You are mixing some topics here. This is about the eclass. I do not see a single argument why the newly introduced inconsistency is superior and makes anything better for the end user. You are just talking about why you did what. Nothing of that contains a technical reason. Are we that politics driven now? In addition... there is no work that needs to be done that has not already been done, other than banning an eclass or stating that it is the way to go. If the eclass is going to be banned, then there is a deprecation phase with a news items for users and devs will just stop using it. If it is the way to go, then nothing has to change (except disallowing ebuilds that break consistency). You are making it sound like there is some huge work to be done. There isn't. And no one has to step up to change the current situation, except the council.
