Wandering Thoughts archives


Why I feel that a missing Debian package is a bad sign

Because someone quoted me, I might as well explain my earlier quick comment about how I consider the lack of a Debian package for a program to be a fairly serious warning sign, and why I specifically picked Debian for this.

Debian has a huge package selection with a fairly large number of people driving it. If a program is still not packaged for Debian, this means that either that it can't attract even one Debian developer's interest or that the program has serious issues of some sort; immaturity, bugs, license problems, it's very hard to build, and so on. Both cases are bad for a busy sysadmin who doesn't want to be out on the bleeding edge, so unless I absolutely need to use the package I am better off passing.

(The exception is small programs that are trivial to compile myself and don't need to be installed; at that point I might as well just try them out, because it's easy.)

My impression is that this signal is pretty much unique to Debian; smaller distributions, Fedora included, don't seem to have the breadth of packages or the depth of packagers. Also, my impression of the Debian culture is that it encourages packaging everything that moves and some things that don't.

(Even if no Debian packager is personally interested in a package, my impression is that Debian users can usually find a developer who will respond to their interest.)

linux/DebianPackageSignal written at 23:19:25; Add Comment

Page tools: See As Normal.
Login: Password:
Atom Syndication: Recent Pages, Recent Comments.

This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.