Re(1): KDE Community Working Group takes care of the community
Posted by: Anonymous
[ip: 213.47.44.9]
on September 07, 2008 01:10 PM
Let's say you want Kopete, well then you have to bring in all of KDE-PIM.
Kopete does not depend on any part of KDE PIM neither at build nor at runtime.
In fact no KDE application as build dependenices outside its source module or kdelibs and while some functionality might at runtime depend on something from kdebase, there is no such dependency between modules.
Acknowledging the runtime dependencies on certain part of kdebase has lead to restructuring the kdebase module so that runtime parts are clearly separate from workspace parts.
It is certainly true that some distributors have repeatedly ignored their users' requests for fine grained packaging, which is why large migration projects such as Munich/Germany decided to go with Debian so they could decide which things to install and which not.
Fortunately this seems to be a thing of the past now and even Novel/SUSE provide single application packages now, no longer forcing their users to install a lot of uwanted things.
This fortunate change of attitude towards users and often customers is probably a nice side effect of Ubuntu which being based on Debian packages with fine granularity mde it obvious to users that the problem lies at their current distributor who could no longer hide behind the myth of bad upstream dependencies.
Learn about Linux
Download Linux
Get Linux help
Re(1): KDE Community Working Group takes care of the community
Posted by: Anonymous [ip: 213.47.44.9] on September 07, 2008 01:10 PMKopete does not depend on any part of KDE PIM neither at build nor at runtime.
In fact no KDE application as build dependenices outside its source module or kdelibs and while some functionality might at runtime depend on something from kdebase, there is no such dependency between modules.
Acknowledging the runtime dependencies on certain part of kdebase has lead to restructuring the kdebase module so that runtime parts are clearly separate from workspace parts.
It is certainly true that some distributors have repeatedly ignored their users' requests for fine grained packaging, which is why large migration projects such as Munich/Germany decided to go with Debian so they could decide which things to install and which not.
Fortunately this seems to be a thing of the past now and even Novel/SUSE provide single application packages now, no longer forcing their users to install a lot of uwanted things.
This fortunate change of attitude towards users and often customers is probably a nice side effect of Ubuntu which being based on Debian packages with fine granularity mde it obvious to users that the problem lies at their current distributor who could no longer hide behind the myth of bad upstream dependencies.
#