Stephen Gallagher wrote: >* The state `dep_enabled` would be set whenever a stream becomes >enabled because some other module stream depended on it. This state >must be entered only if the previous state was `default` or >`available`. (We don't want `enabled` or `disabled` streams being able >to transition to this state.) > >* The state `default_enabled` would be set whenever a stream becomes >enabled because a transaction pulled in a package from a default >stream, causing it to be enabled. This state must only be entered if >the previous state was `default` or `dep_enabled`. We don't want >`enabled` or `disabled` to be able to transition to `default_enabled`. >If a user requests installation of a package provided by a stream >currently in the `dep_enabled` state, that stream should transition to >the `default_enabled` state (meaning that now the user would expect it >to be treated the same as any other default-enabled stream). It looks like a non-default stream could go through the transitions available → dep_enabled → default_enabled. Is that desirable? Björn Persson
Attachment:
pgpSllbfgyUNc.pgp
Description: OpenPGP digital signatur
_______________________________________________ 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
