Linked by Rahul on Sat 11th Oct 2008 01:53 UTC
PolishLinux has an interview with the KPackageKit developers. PackageKit is a abstraction layer over the different Linux package management tools. It is primarily designed to unify the graphical tools and provide a consistent distribution neutral framework for application developers to install add-ons as well. This project was initiated and continues to be maintained by Red Hat developer Richard Hughes who also wrote the initial GNOME frontend to it, called gpk-application. Multiple backends currently exist and it is the default for Fedora and Foresight Linux already. Other distributions including Ubuntu, OpenSUSE, Mandriva, and Gentoo are actively participating in the development of different backends. A KDE interface has been under rapid development recently and just did a 1.0 release last week. This interview provides more details.
Thread beginning with comment 333249
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.
Member since:2005-07-06
but i am of the opinion that if the kde people wants to,
According to what the KDE developers themselves have said for years, your opinion are wrong. They strongly reccomend that the packages are split up for end users. They also go to great length to ensure the build system support this, and maintain strict module separation to make this easier for the distributors.
they can provide for this splitting themselves, rather then having someone at the distro level overrule their decision.
The KDE project only provide source packages, and it's more efficient to provide the source packaged as it's done today doing the splitting with the build system. The recommendation for the distributions are to split up the packages, but the distributions are free to use the strategy they feel supports their users best.
And that Krita and the rest of the KOffice packages on windows are not split, are by all accounts simply a case of not yet done. Not surprisingly since KOffice 2 are still in beta, and that the Windows didtribution team are very small, they have tasks they deem more important.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
yes, it can be both a problem and a benefit.
but i am of the opinion that if the kde people wants to, they can provide for this splitting themselves, rather then having someone at the distro level overrule their decision.
but then there is a counterexample, xorg, where a "split" into sub-projects have made the updating of drivers and introduction of new features outside of full releases easier, it also puts a bigger workload on the distro level to make sure all the pieces fit together.
so its not a one size fits all, but i firmly believe that the decision rests with the maintainers of the code, not the distros, as to how it should be packaged.
having distros overrule the individual projects just muddies the water even more, as one cant say for sure where the problems originate.
but then i guess one should always report to the distro one uses, and let them handle it. but then that kinda puts one at the mercy of ones distro of choice...