Mailinglist Archive: opensuse-kde (169 mails)
| < Previous | Next > |
Re: [opensuse-kde] Cross-desktop KDE packages building - macros
- From: Dirk Müller <dmueller@xxxxxxx>
- Date: Wed, 24 Jun 2009 01:01:18 +0200
- Message-id: <200906240101.18761.dmueller@xxxxxxx>
On Tuesday 23 June 2009, Lubos Lunak wrote:
it is supposed to pull in the KDE runtime dependencies (kdebase4-runtime and
friends) for this particular application to function correctly, and ensure
that at least a particular version of it is installed, namely the one that it
was build against and likely requires it due to C++ ABI.
So you're wondering about the "< 4.2.60" part in the requires? This is not
strictly needed, we added it because we had several people who had
KDE:KDE4:UNSTABLE:Desktop and KDE:KDE4:Factory:Desktop enabled as a repository
and then the solver decided to take decisions that do not work.
I had filed a bugreport to implement to make repositories conflict each other,
but this was rejected, as all dependencies should be expressed in the package
itself. therefore we added this "hack". we can remove the "<" part if that is
the part that worries you.
why do you need kde4-filesystem to be seperate? it is just a list of empty
directories plus this macro file. just link this package should be enough (for
building it does not hurt, you will only get the macros, the additional
directories have no effect).
This was considered but it just does not make any difference to split the
packages, and having just one package that provides all the magic is better
than, well. two.
you can remove the directories from kde4-filesystem for non-suse distros if
that is the other issue, but fedora and mandriva will also want to have those
directories owned (mandriva for sure, not clear about fedora).
Greetings,
Dirk
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx
- The first question is: What is %kde4_runtime_requires actually good for?
I would like to know the exact purpose, since it doesn't quite make sense
to me. As far as I understand it, it is a minimal KDE version requirement,
but this way it is specified by the repository, instead by the application
itself.
it is supposed to pull in the KDE runtime dependencies (kdebase4-runtime and
friends) for this particular application to function correctly, and ensure
that at least a particular version of it is installed, namely the one that it
was build against and likely requires it due to C++ ABI.
Which doesn't make sense to me for most apps, if I build an app
with 4.2, it should work with 4.3 too.
So you're wondering about the "< 4.2.60" part in the requires? This is not
strictly needed, we added it because we had several people who had
KDE:KDE4:UNSTABLE:Desktop and KDE:KDE4:Factory:Desktop enabled as a repository
and then the solver decided to take decisions that do not work.
I had filed a bugreport to implement to make repositories conflict each other,
but this was rejected, as all dependencies should be expressed in the package
itself. therefore we added this "hack". we can remove the "<" part if that is
the part that worries you.
- In order to avoid people copy&pasting the KDE macros all around, I would
like to split them out of kde4-filesystem into kde4-macros. Then people
wanting to use the unified way could just link this package to their KDE
repository. This would provide an easy way to adjust the macros as
necessary. I don't see any big problem here, except for the
mentioned %kde4_runtime_requires needing the KDE version of the repository.
why do you need kde4-filesystem to be seperate? it is just a list of empty
directories plus this macro file. just link this package should be enough (for
building it does not hurt, you will only get the macros, the additional
directories have no effect).
This was considered but it just does not make any difference to split the
packages, and having just one package that provides all the magic is better
than, well. two.
you can remove the directories from kde4-filesystem for non-suse distros if
that is the other issue, but fedora and mandriva will also want to have those
directories owned (mandriva for sure, not clear about fedora).
Greetings,
Dirk
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx
| < Previous | Next > |