Mailinglist Archive: opensuse-kde (169 mails)

[Lubos Lunak <l.lunak@xxxxxxx>]

 Hello,

 a couple of IRC meetings back, we talked about advertising the buildservice 
as a tool for upstream KDE developers to package their applications. As a 
part of this, I have packaged a simple KDE app in home:llunak:kde 
(taskbarswitch) that with the same .spec file builds also for Fedora and 
Mandriva (where same .spec file means there is no conditional stuff per 
distribution).

 So it looks like it shouldn't be that difficult to make it simple for most 
kde-apps kind of apps, where their developers would just create one .spec and 
get it built for all RPM distros, instead of adjusting it per-distro (which, 
of course, would be an option too, but that's more complicated). The trickery 
can be done in macros and in project config (right now 'osc meta prjconf 
home:llunak:kde'). Does this make sense, or do you think it would be better 
to have something that would create the .spec with per-distro code?

 In order to continue, I'd like to do some changes and I have some questions.

-  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. 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.

- 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.

- And then, of course, there is Debian/Kubuntu with a completely different 
packaging system :(. I'm still investigating, but it looks like packaging 
something for both rpm and deb is a big mess. Is here somebody who has any 
experience with packaging debs, preferably in the buildservice?

-- 
Lubos Lunak
KDE developer
--------------------------------------------------------------
SUSE LINUX, s.r.o.   e-mail: l.lunak@xxxxxxx , l.lunak@xxxxxxx
Lihovarska 1060/12   tel: +420 284 084 672
190 00 Prague 9      fax: +420 284 028 951
Czech Republic       http://www.suse.cz
-- 
To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kde+help@xxxxxxxxxxxx