Le mardi 12 novembre 2019 à 16:09 -0500, Stephen John Smoogen a écrit : > On Tue, 12 Nov 2019 at 15:36, Stephen Gallagher <sgallagh@xxxxxxxxxx> > wrote: > > On Tue, Nov 12, 2019 at 12:40 PM Stephen John Smoogen < > > smooge@xxxxxxxxx> wrote: > > > > > The technology allows you to do this. The policy can restrict this. > > Of > > course, this particular example can be true of a non-modular RPM > > too; > > you don't *have* to build the X-devel subpackage. > > > > I am asking these questions this way because of 20 years of RPM > fights > of people arguing over things because a spec file is a combination of > a policy document and a technical document but people like to treat > it > as one or the other in the conversations. Getting it clear when you > are speaking about the technical implementation of policy or the > political implementation of technology up front gets that out of the > way. Not being clear is where people start building their own mind > castles to send armies of strawmen against. I don’t think it’s that easy to distingish tech from policy. No one wants a broken policy. Therefore, a successful policy is intrinsically linked to the implementation that makes it work. More often than not, what people call policy, is the human part of the implementation. Automate this part one way or another, and people will claim it's a tech artefact. A whole (human + tech) works or not. Trying to define where the frontier is within this whole does not bring a lot of value. The two parts are two faces of the same coin (see also: Conway's law). More generally, that means that trying to rip rpm from the Fedora project, or the Fedora project from rpm, is doomed to failure. Creating a new project around rpm will evolve into something very close to Fedora/Suse/etc. Creating a new deployment tech within Fedora will evolve into something very close to rpm (different implementation, same behaviour). Changing either Fedora or rpm requires making both the org, and the tech, evolve gently in lockstep. Regards, -- Nicolas Mailhot _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
