[Build-common-hackers] Bug#520383: Bug#520383: Bug#520383: kde.mk is not KDE4?compatible

[Jonas Smedegaard]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Sune,

[Sent to Sune+bugreport: Peter and me as CDBS maintainers need no cc]

On Sat, Apr 11, 2009 at 01:10:02AM +0200, Sune Vuorela wrote:
>(Better a late reply than never)
>
>On Thursday 19 March 2009 12:27:04 Peter Eisentraut wrote:
>
>> I wanted to discuss the KDE 4 integration as well.  I don't mind if 
>> the KDE team maintains the class for KDE 4 (if they really want to 
>> and are not simply afraid to interact with the cdbs maintainers, I 
>> hope).
>
>We have until now wanted that we were controlling the arguments that 
>kde is built with (what we have in variables.mk)
>I'm not really scared of you, the cdbs maintainers, but I do sometime 
>hope that you would act a bit faster on reports.
>
>> But it would be better to keep the paths consistent.  It is useful to 
>> be able to do ls /usr/share/cdbs/1/class or the like.
>
>So far, I have tried to avoid entering the cdbs dirspace - and pushing 
>it into cdbs would also require cdbs to add a dependency on 
>pkg-kde-tools, as we still have our variables.mk that sets the 
>configuration variables.
>And that directory is also already filled with a file called kde.mk 
>that does some quite different.

You can distribute the kde snippet yourself, if you prefer - like quilt 
does.  We just recommend that you use the cdbs path so that users of 
your cdbs snippet more clearly recognize it as following cdbs v1 api.

We can also distribute the snippet - we can suggest rather than depend 
on your package, just as we do not depend on autotools, cmake, gnome or 
other tools that we provide snippets for.  The user of the snippet will 
need to build-depend themselves on the additional tools required for 
that snippet to work.

That said, it makes most sense to keep snippet and its defaults shipped 
together.

What I would find ideal is if the both files was shipped with cdbs, and 
some of you KDE guys joined our team to be able to maintain the defaults 
whenever you found need for it.

(or actually, what I _really_ would find ideal was that we changed to 
using Git at the collab-maint area at Alioth - and all Debian developers 
in your team could update the defaults directly - but we haven't 
discussed Git and collab-maint at all in our team yet)

Alternatively I would recommend you do as quilt: Ship both defaults and 
the snippet yourself, but use common cdbs dir for the snippet.

As a transition, you could place a wrapper snippet at the old location, 
that a) included the snippet at the new location and b) emitted a 
deprecation warning recommending to use the new location)


I'd be happy to help with the details if needed.


>I'm not sure how to proper integrate pkg-kde-tools into cdbs and still 
>offer the default compilation variables to people not using cdbs, for 
>those who needs that.

Ah, off course: you want a single file with defaults shared for cdbs and 
non-cdbs use.  You want the quilt approach!


Kind regards,

 - Jonas

- -- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  [x] quote me freely  [ ] ask before reusing  [ ] keep private
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknf27QACgkQn7DbMsAkQLgV1QCggiCvKS5H/w9IYrXN8DgBqsEu
zGoAn1FXgYSTSmSM3IbLUT7G5IRWXm2Q
=4PbU
-----END PGP SIGNATURE-----