Commentary

Serdar Yegulalp
 

Making Linux Binaries Simple: Automate 'Em

If Linux doesn't change its attitude about prepackaged binary (read: closed source) software anytime soon, here's a suggestion: a generic software deployment system for Linux binaries.

If Linux doesn't change its attitude about prepackaged binary (read: closed source) software anytime soon, here's a suggestion: a generic software deployment system for Linux binaries.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The idea came about when talking with a couple of commercial software vendors, all of whom had Linux products and who all tacitly admitted that one of the biggest problems with making Linux editions of anything is supporting each individual distribution. You either have to pick a distro and stick with it, build binaries for every major distro and ever major revision of each distro, or just give up and make your app open source.

My idea: Create a generic Linux software-building system. It uses virtual machines and automated build scripts to take a single source package, build it across all the major Linuxes at once (Red Hat, Debian, SUSE, plus whatever else you want to add), and generate reports for each. It could also test-run the software directly on the build itself and generate statistics or notes about its performance. It might even be able to fetch build / code optimization hints from a central database, so that notes about what works best where could be crowdsourced.

From what I can tell, there's a real need for stuff like this. The more I talk to third-party software vendors and developers and Just Plain Users, the more obvious it becomes that Linux has been built in such a way that it's not just indifferent to commercial software but actively hostile to it. This is only likely to get worse as it goes on, not better.

I mention this to those not in the business of creating commercial softwre and I typically get a response along these lines: "Well, Linux isn't a commercial software ecosystem; it's its own animal." Which is fine, but that still doesn't afford much comfort to the people who try to deploy or run a closed-binary app on Linux, and have to jump through no end of hoops to do so. The whole thing is still slanted strongly towards apps distributed as source and built to binaries by each respective distribution.

What I'd really like to see best, though, is Linux get to a point where jumping through such hoops would no longer be needed. But for now, this is my suggestion.

InformationWeek has published an in-depth report on Sun's future under Oracle. Download the report here (registration required).

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