Ideas for progress:

- [ ] Open a [ticket at Fedora Packaging 
Committee](https://pagure.io/packaging-committee/issues) or better send a PR to 
[File and Directory 
Ownership](https://docs.fedoraproject.org/en-US/packaging-guidelines/#_file_and_directory_ownership)
 
([source](https://pagure.io/packaging-committee/blob/master/f/guidelines/modules/ROOT/pages/index.adoc#_1379))
 explaining why `%exluding` files completely from packages is dangerous and not 
intended to work and that it MUST not be done.
- [ ] Work with @voxik to change the rubygem package generator.
- [ ] Work with me to solve the Python namespace package issue. For example in 
[this bugzilla](https://bugzilla.redhat.com/show_bug.cgi?id=1935266). Maybe 
`%ghosting` is a way to go.
- [ ] Open a ticket on 
[rpmlint](https://github.com/rpm-software-management/rpmlint/) to detect 
completely `%exluded` files. Not sure if it is technically possible, but worth 
a shot.
- [ ] Open a ticket on [FedoraReview](https://pagure.io/FedoraReview) to detect 
completely `%exluded` files. Should be possible.
- [ ] In `%files`, collect the list of `%exluded` files and see if all of them 
are actually packages somewhere. If not, issue a warning that could be knob-ed 
to an error.

Note that those ideas are not dependent on each other and can happen at 
different timelines.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/994#issuecomment-815552109
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to