On Mon, Sep 28, 2015 at 3:57 AM, Martin Vaeth <mar...@mvath.de> wrote: > Rich Freeman <ri...@gentoo.org> wrote: >> >> Sure, but the portage team can really only dictate the upstream >> defaults of portage, not tree policy. > > As I understand, they intend to remove non-dynamic deps > (if they agreed to not implement it properly for sub-slots, > this makes sense). > > So we are not speaking about defaults but a fixed behaviour of > portage. Paludis had this fixed behaviour since ever. > Thus, esssentially, there is no other choice than to adopt the > necessary tree policy to the only existing implementations - > not council decision is needed for it unless there are package > managers which do it differently.
Like I said, we can either have a formal decision, or listen to everybody fight WW3 over it for three years. What is the value in doing the latter? The fact that none of the package managers work with a tree practice won't stop developers from doing it anyway. Plus, any of them can just fork portage and put that in the tree - there is no policy that states that there can be only one implementation of portage. Heck, they could just follow the same upstream and patch it in the ebuild. People seem to think that just going and imposing a change on everybody else without their input somehow makes things more efficient, or less political. The reality is that it just results in more politics, since many will not accept the validity of their actions. It also isn't how we do things around here. If you want to change tree policy, propose it on a list, let everybody have their say, and then if necessary let the council impose a decision. People might not like the decision, but most devs will at least respect the legitimacy of it. If they don't respect the decision they can be booted, and the council will back that up. This isn't about who is or isn't right, or whether the portage team knows what they're doing. This is about having a process (GLEP 39) and following it. The portage team can do whatever they want with portage (after all, nobody has to use portage), but if they want to change what everybody else is doing with their ebuilds they have to follow the process. -- Rich
