Hi Petr, Thanks very much for the detailed reply. The process is a lot clearer to me now. On Mon, Jul 22, 2019 11:24:49 -0000, Petr Pisar wrote: > On 2019-07-20, Ankur Sinha <sanjay.ankur@xxxxxxxxx> wrote: > <snip> > > > 3. And finally: version 2.18.0 is already available in the repos (the > > platform?). So, did I mess up by requesting a stream for this version > > too? How do I make this the "default" module? File a FESCo ticket and so > > on? > > > I believe that it's not allowed to override a non-modular package by > a modular one in Fedora. I also believe that Fedora still does not > support having modules in non-modular build root repository. > > If these assumptions are correct, you have two choices: > > (1) Retire nest package in non-modular Fedora and make the 2.18.0 stream > of the module a default one by submitting a pull request with the > definition to <https://pagure.io/releng/fedora-module-defaults.git>. > A drawback is that anybody who wanted to use nest for building his > packages will have to modularize them first. > > (2) Just don't create any default stream of the nest module. People will > stil use the non-modular one. Those who needs a different version > can enable a particular stream themselves on their systems. You also > don't have to submit the 2.18.0 modular build to Bodhi if you do not > want to maintain it in addition to the non-modular nest package. OK. That makes sense. I'll go with (2), since we do want NEST as a non-modular package that users use by default (with or without modularity). In the meantime, this was filed: https://bugzilla.redhat.com/show_bug.cgi?id=1732531 "On Fedora Rawhide, the nest module does not have the default profile(s) set. Therefore, DNF will not install the module using `dnf module install librealsense`. It will only enable it. Since modules should be able to install using the aforementioned command, I consider this a bug." (sic) Now, I'm not clear on this. Must a default stream be defined? The documentation does not clearly specify this: https://docs.fedoraproject.org/en-US/modularity/making-modules/managing-defaults/ If yes, how does one go about it in this case: if the non-modular version is the default that we want users to use, what should be the default module? Given that 2.18.0 is already the non-modular version that we want users to get by default, should I define 2.16.0 as the default module? But then, wouldn't this confuse users? -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
