Re: Modularity and the system-upgrade path

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ben Rosser wrote:
> Before things are rolled out further, I'd like to see some policies
> agreed upon for what modularity is and isn't allowed for in Fedora:
> what are the rules for default streams, buildroot only modules,
> modularizing non-leaf packages, etc.

So, to start that discussion, I think all 3 of those should be no gos in 
Fedora. In other words, I propose the following rules:
* no default streams, use "ursine" (non-modular) packages for the default
  versions instead (you may ALSO ship the same version as a module, if that
  makes it easier for you, i.e., if it means you don't have to retire and
  unretire module versions at every release, but the "ursine" version must
  exist),
* no buildroot-only modules nor buildroot-only packages in modules,
  everything used to build packages must be shipped along with them,
* no non-leaf modules, since those unavoidably lead to version hell due to
  the non-parallel-installability of different versions of the same module.

        Kevin Kofler
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux