On Thu, Nov 14, 2019 at 8:19 PM Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: > > Stephen Gallagher wrote: > > Modular packages without defaults makes sense if they have > > dependencies on a non-default stream. For example: ReviewBoard depends > > on the Django:1.6 stream because of complicated upstream reasons. I > > have to choose between "modular without a default stream" or "not > > available on Fedora", because we have agreed on a prohibition on > > default streams with dependencies on non-default streams. > > The right fix would be to package Django 1.6 as a parallel-installable > compatibility package instead. I don't see why I cannot install ReviewBoard > together with another Django web app on the same web server (without > containers/VMs). (Admittedly a hypothetical example because I am running > neither ReviewBoard nor another Django app on a server I maintain. I also do > not run Fedora on a server. But if I were faced with this issue as a server > administrator, I would curse loudly at Fedora and switch the server to a > distribution that does not get in my way that way.) > The only really reasonable ways to do that would be to support a mechanism to package virtualenvs or do mutations to vendor it with the app. Either way is uglier than the modules mechanism. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ 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
