The Future of Packaging Software in Linux
michuk writes "There are currently at least five popular ways of installing software in GNU/Linux. None of them are widely accepted throughout the popular distributions. This situation is not a problem for experienced users — they can make decisions for themselves. However, for a newcomer in the GNU/Linux world, installing new software is always pretty confusing. The article tries to sum up some of the recent efforts to fix this problem and examine the possible future of packaging software in GNU/Linux."
I have always wondered why bright minds, working for "free" and able to produce an OS that is giving corporations with big budgets a run for their money, cannot agree on how best to package software. To many users, we in the Linux world are still a bunch of jokes.
Sadly, it appears that because of bigotry, selfishness and ego, it will be a few more years before those that command authority in the Linux world wake up. I hope we'll still be relevant by then.
This reminds me to digress a bit...Joe User asks for an improvement in GNOME's file dialog, which is still very wanting and is instead met with the poisonous "I know it all" attitude.
I hope your post was not meant as flamebait, because otherwise I am tempted to munch on it bait hook and sinker.
How does an MSI installer handle dependencies? Somewhat like: "If this DLL is not ours, just overwrite it 'cause our version is better?"
How does an MSI installer handle updates? Somewhat like: "No need to, the user will know it's time to go look for an update when the next worm or Trojan hits?"
Etcetera, etcetera.
If you like apt and get dependency hell, enter the 21st century and use aptitude or synaptic. Both offer you ways of resolving dependency problems, aptitude currently being the most sophisticated.
Need to know about software updates? Install update-manager or kpackage.
The Hacker's Guide To The Kernel: Don't panic()!