On Fri Dec 2, 2022 at 13:30 -0800, Adam Williamson wrote: > What does everyone else think? Has the time come? Or is there more we > need to do to make side tags usable for all cases before getting rid of > overrides? -1. For many use cases, side tags are the correct solution and buildroot overrides should not be used. However, there are occasions where they are still useful. If people are improperly using buildroot overrides and breaking the buildroot, the correct solution is education and documentation, not banning them entirely. Examples: 1. There is a Go compiler release that has patches for a CVE (i.e. almost every Go release ). I create buildroot overrides so all new builds are able to immediately start using it. 2. The same thing above but with other Go libraries that are statically linked into Go binaries. 3. There is a bug in macros that break builds. The fix should be available in the buildroot for all new builds immediately. 4. Some other buildtime only dependency update provides a bugfix that is needed for packages that BuildRequire it. On Fri Dec 2, 2022 at 23:21 +0100, Fabio Valentini wrote: > Not sure if we should turn them off entirely, but we could restrict > their use somewhat? For example, only allow people in "releng" or "qa" > groups to file them. I'd prefer not to have to bother releng every time I need to do this. -- Maxwell G (@gotmax23) Pronouns: He/Him/His _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
