RHX: Package Management Fully Realized?

Share via Twitter Share via Facebook Share via Linkedin Share via Reddit

In an interview with Red Herring yesterday, I claimed to be “outspoken” on the subject of a Linux “repository.” I’ve already gotten one question on that rather cryptic quote, so let me explain.

For several years now, I’ve been making the argument that package/application management is a significantly differentiating feature for the operating system. More specifically, it differentiates Linux – which has both officially sanctioned package management applications and community repositories behind them – from Solaris and Windows. It’s a significant advantage, in my view.

Linux users can install and maintain literally thousands of applications without even leaving the command line, while Solaris (unless they’ve gone the Blastwave route) and Windows users are more or less on their own for application procurement, patching and management.

Despite this seemingly impressive feature, you’ll rarely if ever hear this touted by Linux advocates; perhaps they simply take it for granted given that many if not most Linux admins have never known a distro without it. As a result, my recommendations that Linux distributions press their advantage in this area by leveraging existing infrastructures to connect to both commercial and community oriented repositories more or less fell on deaf ears.

In the summer of 2005, as an example, I recommended that Red Hat integrate their Network offering with yum to begin the convergence of commercial and non-commercial libraries. While the Red Hat folks were polite, they also seemed rather unimpressed with the idea.

They were not alone. Generally speaking, when I’ve spoken to commerical Linux providers on the subject, I’ve been told that a.) customers don’t have interest in a wider network of applications, or b.) community offerings threaten our commercial network. I tackled the latter point in the piece linked to in the above paragraph, saying:

Q: But isn’t there the possibility that these application management facilities will compete with commercial versions, such as the Red Hat network?
A: Great question. The answer, in my opinion, is no. Here’s why:

  1. I accept as a given that community maintained libraries will always be more comprehensive and long tail-ish than commercial equivalents
  2. I further accept as a given that big commercial entities would prefer to pull their version of, say, MySQL from a commercial network versus a library maintained by individuals without commercial needs in mind
  3. I accept as likely that commercial ISVs would prefer to work with commercial networks

In short, I think there’s an excellent opportunity for commercial and community networks to function seamlessly side-by-side, each serving different needs and having different strengths…Either network by itself is incomplete, in my view. Commercial networks will always lag non-commercial ones in terms of application breadth and depth, and non-commercial networks are unlikely to be perceived as a viable basis for higher end enterprise needs.

That commercial and non-commercial networks can operate side-by-side in a complimentary rather than zero sum fashion I think is better understood and appreciated. But what about the first objection – customer demand? Are customers interested in a network of applications to be supported and offered from the operating system vendor?

If the Red Hat Exchange (rhx) is anything to judge by, the answer is yes. I have yet to speak directly with the folks from Red Hat on the subject, but from the outside looking in this appears to be an excellent first step towards realizing the potential advantage Linux has always enjoyed in the package/application management space.

Microsoft is living proof that a platform ecosystem and the inertia therein is the best defense against would-be rivals, but Red Hat seems poised to exploit precisely that strategy at the expense of Windows, not to mention Solaris. This is obviously important for Red Hat; like Eclipse, it has moderate immunity to would-be challengers simply by virtue of its ISV commitments, and this could make that already strong story stronger. What is perhaps less obvious is how significant a development this could be for the greater open source ecosystem: simplified entry-points to Red Hat’s installed base? As Matt says, not a bad opportunity.

Anyhow, will be checking in with the Red Hat folks ASAP to see whether or not my expectations are born out or merely wishful thinking.