Debian Packaging Policies
The cluster centers on debates about Debian's conservative packaging practices, maintainer decisions, volunteer-driven development, bug handling, and comparisons to Ubuntu, with defenses against criticisms of slowness or deliberate choices.
Activity Over Time
Top Contributors
Keywords
Sample Comments
What problems have you faced from Debian's approach?
What is Debian missing and why is it Ubuntu's fault that it isn't in Debian?
Why do you assume Debian packagers don’t do the same?
Disappointing that Debian seems completely uninterested in this :(
That's why we have Debian!
People,This is great news for few of us.But it has been hard to read trough this comments and realize how much ignorance about what Debian is, how it works, what the Debian bug tracker is, what a voluntary-based project is, and to read some assertions and prepotency around in HNIf you see ANYTHING wrong with Debian, go fix it, or shut up and go to sell your stuff to another one.Debian is not a startup. Debian is not an elastic architecture in the cloud to support/pay-for traffi
Do you know why debian did that? Any links to debian-devel threads?
Well, this is Debian - they generally don't maintain the software, they just package it. Small changes can be pushed upstream, but "Here's a brand new build system that we promise is super cool" is generally not a patch that people like taking :)
... and Debian is very serious about it: https://fulda.social/@Ganneff/112184975950858403
Does Debian benefit from this work?