On Wed, Aug 10, 2011 at 9:31 PM, Dirk Müller <dmueller(a)suse.de> wrote:
On Tuesday 09 August 2011, todd rme wrote:
Can somebody explain the purpose of
it is a central package that has multiple purposes:
- define common macros for all kde like packages
Yes, I said I understood this.
- define ownership for common directories for all kde
This, in some cases, is something I don't understand. For example,
why are the kdelibs directories not defined by kdelibs? Or the oxygen
icon directories not defined in the oxygen icons package?
It seems that having the directories separate from what actually uses
them makes the packages more difficult to.
It also adds needless dependencies for users. Why do users need to
worry about rpm macros unless they are building packages?
why the library directories are generated there rather
than in the kdelibs package, or why, for example, obsoletes of kdsdk4
packages are put there rather than kdesdk4.
Because kdesdk4 does not exist anymore, so something has to obsolete it.
Maybe that isn't the best example. How about libkscan4? This is
already provided and obsoleted by kooka. Or kdedue4. Shouldn't this
be obsoleted and provided by libkdeedu4?
Is there a problem with that?
I'm trying to do a cleanup of the KDE packages (RPMLINT errors,
formatting issues, macro usage, etc) and I am trying to understand
what I should and should not be cleaning up in this package.
The obsoletes, in particular, lead to a lot of unnecessary rpmlint
errors. If these were, wherever possible, put in the appropriate
packages, then they could also give the necessary "provides", but
adding provides to kde4-filesystem is definitely wrong, since it
doesn't really provide anything.
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org