Commentary

Serdar Yegulalp
 

Debian And Ubuntu Flaunt Their Package Popularity

Two "popularity contests" in the Linux world aren't what you might think they are -- they don't track Linux's appeal at large, but rather who's installing what packages from a given Linux distribution. The results are still somewhat raw and subject to different interpretations, but eye-opening nevertheless.

Two "popularity contests" in the Linux world aren't what you might think they are -- they don't track Linux's appeal at large, but rather who's installing what packages from a given Linux distribution. The results are still somewhat raw and subject to different interpretations, but eye-opening nevertheless.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The Popularity Contest works like so: In both Debian and Ubuntu, you can participate in sharing your package usage statistics by installing a package named popularity-contest (obvious, right?) from the main repository. The data's anonymized, sliced and diced a couple of different ways, and served up with regular updates.

Bruce Byfield over at Datamation originally posted about the contest, so I headed on over to the Debian and Ubuntu stats pages and took a gander at what they had to offer. The most basic breakdowns are by processor architecture (i386 is way out in front, naturally) and by repository -- and, of course, by the differences in package selections between the Debian and Ubuntu crowds. The main difference between the two distros: the Debian folks seem to avoid unfree binary blobs whenever possible.

Again, a lot of the data provided could probably stand to be filtered a little more closely. One filter in particular I'd like to see would be one that ignores the core stuff -- the kernel, the toolchain, etc. -- and focuses on actual user applications that people run in a daily fashion. Such a refinement probably will have to wait until the next iteration of the popularity contest, though.


Follow me and the rest of InformationWeek on Twitter.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links