On 2019-10-04, Miro Hrončok <mhroncok(a)redhat.com> wrote:
Wouldn't it be easier if the "default stream" would
just behave like
a regular package?
I can think of two solutions of that:
1. (drastic for modular maintainers)
We keep miantaining the default versions of things as ursine packages.
We only modularize alternate versions.
That effectively bans modules with multiple dependencies where at least
one is a default version.
Example: I have Perl 5.26 as a default version. I have Perl 5.30 as an
laternative version. Now I want to package Bugzilla that's written in
Perl. How do you package Bugzilla so that it works with Perl 5.26 as
well as with Perl 5.30?
If each of the Perls is a stream of a module, you will put Bugzilla into
a module and let it depend on any of the Perls. User can install any of
the Perls and Bugzilla.
With your proposal Bugzilla packager would have to package Bugzilla
twice: as a normal package for default Perl 5.26 and as a module for Perl
5.30. Then a user would have hard time to select the right combinations of
Perl and Bugzilla. It would double fork work pacakgers and and make
the system more dificult for users.