=== A module does not have one or more of its profiles specified to be
> the default. ===
>
>
Here, I would expect that DNF will finish with error, advising the user to
select a profile specifically, such as using "dnf module install
<module>:<stream>/<profile>".

 === A module has explicitly set one or more of its streams to have no

> default profiles ===
>
>  Here, I could imagine that such a module would be marked "special".
Marking a module "special" would clearly tell QA that special behaviour is
intented (empty profile or something similar). The DNF either should not
list them in "dnf module list" or if listed they should have a visible
distinction (such as "s") or something like that. We could utilize the
difference between "dnf module list" and "dnf module list --all", that
currently do the same job, so that "dnf module list" would only show
installable modules, while "dnf module list --all" would list all modules,
as the option suggests.
If someone attempted to install a special module, DNF should not proceed
anyhow and warn about that.


> === A module has a profile that contains zero RPMs ===
>
>
See above. This should be a typical example of a "special" module.




> In this case, a profile definition has been made in the module
> metadata and it explicitly contains zero RPMs within it. Such an
> example might be for compatibility: the module previously provided a
> profile with that name that contained content, but it is no longer
> doing so. Retaining the name may have been done to allow existing
> scripts to avoid breaking. If we have a profile that contains zero
> packages, should it be an error if we attempt to install it? If not,
> what should the UX look like?
>
>
> [1]
> https://communityblog.fedoraproject.org/modularity-hackfest-march-2019/
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>


-- 

Lukáš Růžička

FEDORA QE, RHCE

Red Hat

<https://www.redhat.com>

Purkyňova 115

612 45 Brno - Královo Pole

lruzi...@redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to