https://pagure.io/packaging-committee/issue/1232 Vít Dne 02. 11. 22 v 9:14 Petr Pisar napsal(a):
It used to be a good practice to announce changes in Packaging Guidelines <https://docs.fedoraproject.org/en-US/packaging-guidelines/> here on this list. The forkflow was that Fedora Packaging Committee accepted a change on it's meeting and then announced it in their meeting notes posted here. This workflow allowed packagers to notice the changes and apply them to their packages. However, this is not true anomore. E.g. In February a ban for wildcard %files was augmented from dynamic libraries to all top-level files <https://pagure.io/packaging-committee/c/2bc90a6463ae591ed134955485da0596c2fe958b>: commit 2bc90a6463ae591ed134955485da0596c2fe958b Author: Carl George <carl@george.computer> Date: Wed Feb 2 18:52:03 2022 -0600 Adapt Python's explicit lists guidance to the main guidelines diff --git a/guidelines/modules/ROOT/pages/index.adoc b/guidelines/modules/ROOT/pages/index.adoc index 2bb4f9e..5ec0896 100644 --- a/guidelines/modules/ROOT/pages/index.adoc +++ b/guidelines/modules/ROOT/pages/index.adoc @@ -2574,6 +2574,27 @@ The %defattr directive in the %files list SHOULD ONLY be used when setting a non-default value, or to reset to the default value after having set a non-default value. +=== Explicit lists + +Packagers *SHOULD NOT* simply glob everything under a shared directory. + +In particular, the following *SHOULD NOT* be used in `+%files+`: + +* `+%{_bindir}/*+` +* `+%{_datadir}/*+` +* `+%{_includedir}/*+` +* `+%{_mandir}/*+` +* `+%{_docdir}/*+` To my surprise the first time when I get known to this new rule was today in a review of my new package. It could be that my memory failed. So I checked FPC and found these two relevant issues: <https://pagure.io/packaging-committee/pull-request/1160> <https://pagure.io/packaging-committee/pull-request/1161> Which do not contain any description or summary. Simply bunch of "+1" comments. Then I searched a February archive of this list and found these three FPC posts: Schedule for Thursday's FPC Meeting (2022-02-03 17:00 UTC) <https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/CCEMBTZ5BQPMNSO5HV65YAJXWE6SCPXU/> Schedule for Thursday's FPC Meeting (2022-02-10 17:00 UTC) <https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/QTJ5HGIEMSNWLHP2VOQXSMUJ3PIOG3FC/> Schedule for Thursday's FPC Meeting (2022-02-17 17:00 UTC) <https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/KVWWWYV3H4EG75OCIMKPUVBGCCMINGOY/> None of them mentions this change. Could we please resume announcing substantial changes in the guidelines on this mailing list? -- Petr _______________________________________________ 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
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ 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
