Linked by Thom Holwerda on Wed 26th Jan 2011 22:24 UTC, submitted by fran
Thread beginning with comment 459848
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
The system they're proposing here is a wrapper that hides the different package managers under a common interface with features that appeal to end-users.
I haven't read the article yet, but isn't that what PackageKit does? I've use KPackageKit on Kubuntu (apt backend) and Arch (pacman backend) and it works just the way you say: unified front-end that's easy to use, but that queries the distro-specific repos.
I haven't read the article yet, but isn't that what PackageKit does? I've use KPackageKit on Kubuntu (apt backend) and Arch (pacman backend) and it works just the way you say: unified front-end that's easy to use, but that queries the distro-specific repos.
In fact they'll use PackageKit, but their going to change the UI and rely on other services to provide info.
I see Linux being used in 3 places:
embedded OS (hardly ever gets updated, so no repository needed, let alone an appstore)
server OS (updates sometimes come from a repository but not always and an appstore is not needed)
"Grandma's Desktop OS" (or more commonly refered to as "Geek OS"/"No virus OS"/"Cheap OS" where this article is all about
Indeed a small part, but the only part relevant here




Member since:
2006-06-21
I don't think that will ever happen. Different distributions cater to different audiences and purposes. And each distribution has different branches, at the very least a "stable" and a "development" branch; most of them more than two.
The system they're proposing here is a wrapper that hides the different package managers under a common interface with features that appeal to end-users. It's great they're doing this wrapper but it's just a specialized app that caters to a niche audience. Do not expect major architectural changes to go with it.
It does not mean package managers will be unified, ever, or that distributions will give up their own goals and development process just for the sake of dumping everything into one big repository.
Furthermore, power users and developers will need to keep using the power tools of the package manager. They need the extra information, or to automate update and upgrade operations, or to fine-tune the way the manager works, be able to access it from the console etc.
Please remember that Linux is very flexible and is being used by lots of people in lots of different ways. "Grandma's desktop PC" is just a small part of it.