Zbigniew Jędrzejewski-Szmek wrote: > we should allow bundling for consistency, and I also disagree with the > reasoning raised by other people that we must _not_ allow bundling because > that'll create a slippery slope to use it everywhere. Bundling has been done very conservatively up to this point and its only caused a ton of extra work which fewer people want to do. Lots of Fedora package maintainers are already spread across a dozen packages for which they often don't have the time to properly maintain and most of the time no one cares because there are only a handful of people using it or any programs that consume it hasn't been update either. In my honest opinion this is not a matter of *if* bundling should be allowed but *when* and *how* > As discussed in the other part of the thread, more reasonable language > ecosystems deal very well with unbundling. (Or rather, don't do > bundling in the first place.) For Python and Rust we certainly don't > want to do bundling. (In particular, for Python pip and conda were > mentioned. Those are interesting examples. Conda is dying. OTOH pip > and the rest of the Python ecosystem switched to declarative > dependency specification to allow interoperability with distributions. > So in fact it is a counterexample to the statements that modern > language ecosystems are incompatible with traditional packaging.) > Zbyszek What is a "reasonable" language ecosystem here? Rust sure isn't, I can see at least 6 (0.9, 0.11, 0.12, 0.13, 0.14, 0.15) versions of the rust-hashbrown package in Fedora 41 which all need to be maintained separately and if someone wants to package something that depends on 0.10 then they need to start maintaining that as well. Python suffers from the same except its an interpreted language so you can't have multiple versions of the same package installed side-by-side, so I guess someone either needs to vendor a dependency or update it to a newer version by themselves. Go's ecosystem is even more annoying because its decentralized and anyone can do whatever they want so a dependency may be provided through a github link or through a link to their website. The only place where packaging dependencies makes sense is when they leave non conflicting artifacts which can be reasoned about. -- _______________________________________________ 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
