On Thu, Jan 21, 2021 at 4:51 PM Kevin Kofler via devel <devel@lists.fedoraproject.org> wrote: > > Florian Weimer wrote: > > This is closer to the existing policy, I think: > > > > <https://docs.fedoraproject.org/en-US/packaging-guidelines/#bundling> > > Actually, the very first 2½ sentences at that link make my point even more > clearly than the link I had posted: > > | Fedora packages SHOULD make every effort to avoid having multiple, > | separate, upstream projects bundled together in a single package.
You mean like "python-s3transfer", which bundles multiple multiple python modules together for no intelligible reason, requiring hand-tuning of packages like "awscli" which have to seek out the relocated modules? The guideline has sometimes been ignored for reasons that are not compelling. > | All packages whose upstreams allow them to be built against system > | libraries MUST be built against system libraries. > | > | All packages whose upstreams have no mechanism to build against system > | libraries MAY opt to carry bundled libraries, […] > > I do not see with what justification you want to argue that this Rust > package has no upstream mechanism to build against system libraries, > considering that there is a non-vendored tarball. > > Kevin Kofler I personally agree with your logic. I wish it were applied more consistently, where additional libraries would be more consistently published as their own system library. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
