On Thu, Nov 3, 2022 at 12:02 PM Michael J Gruber <mjg@xxxxxxxxxxxxxxxxx> wrote:
While it is annoying to spell out each file it does catch package changes which might go unnoticed otherwise. In particular, we've had a few unannounced soname changes and such lately. [Disclaimer: I have not checked whether the maintainer ignored the build failure for an explicit soname or got trapped by a wildcard in these cases.]
But the packaging guidelines already mentioned not globbing the soname part of the files, so this change makes no difference to that use case. Extending the no-globbing rule to other directories like datadir seems very excessive. Why should we have to list all files a package wants to ship as its data?
-Ian
We could probably live better with wildcards if proper rpmdiff-tools were part of the workflow and of gating or such. Those would be the right tool for the job.
_______________________________________________
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
_______________________________________________ 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
