On Fri, Sep 11, 2020 at 11:03:39AM +0200, Hans de Goede wrote: > An other more generic approach which has been brought up once or > twice, but which not really has been discussed in much detail yet > I believe is creating a fedora-builddep repository. > > ATM a normal user has 3 ursine Fedora repos installed: > > fedora > fedora-updates > fedora-updates-testing (disabled by default) > > What if we add a 4th repo called fedora-builddep: > > fedora > fedora-updates > fedora-updates-testing (disabled by default) > fedora-builddep (rolling (within a release), disabled by default) > > So the idea is that all the maven deps which you need, but > do not want to offer any end-user support on would go to > fedora-builddep. If we absolutely must have build-only packages, we can do it more simply: insert Requires: fedora-unmaintained-package or Requires: fedora-buildonly-package (name TBD), and beef up dnf a bit to explain that "this package cannot be installed because it's only maintained at the level appropriate for building packages...". I think there are two advantages: first, no need for a separate repo, so there'll be less infra change and churn. Second, this tag can easily set on each subrpm, without any central list to manage. Zbyszek _______________________________________________ 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
