OK, getting kdebindings4 rolling up

[Adeodato Simó]

Hey there. Since you both thought maintaining the Ruby and Python
bindings of KDE4 from the pkg-kde repository was a good idea, we've
added you to the project in alioth, so by now you should have commit
access already.

So, some notes:

  * pkg-kde keeps its packaging in SVN; for kde4 stuff, the location is
    under branches/kde4. Hence, the place to keep kdebindings would be:

      /branches/kde4/packages/kdebindings (and a debian/ directory inside that)

    AFAIK nothing like svn-buildpackage is used by the members of the
    group.

  * normally cdbs is used for the packages, but I see you both keep
    version 3 of the bindings under debhelper only, so I think that'd be
    fine for version 4 as well. bindings are always special, so...

  * the source package name should be something different to
    "kdebindings", in order to have it uploadable to unstable, and
    co-installable with KDE3 stuff (binary packages will also be named
    differently, but that's obvious). I've gone with kde4bindings, for
    consistency with kde4libs.

    @Vincent: the KDE 4 development platform (kdelibs5 and stuff) is
    expected to hit unstable in a couple weeks (it's in experimental at
    the moment), so after that bindings can be uploaded to unstable
    themselves. About the rest of KDE 4, there's a mail to d-d-a in the
    cooking.

  * if you would like help with any generic packaging stuff of
    kdebindings, I should be around to lend a hand, or act as backup.
    Also, the pkg-kde members hang out in #debian-qt-kde in irc.d.o,
    should you need to contact us by irc. Also, discussion via email
    takes place on this list (pkg-kde-talk at lists.alioth.debian.org),
    rather than debian-qt-kde at lists.debian.org (which is mainly for BTS
    traffic).

    This Alioth lists is quite low traffic, so if you'd like to
    subscribe... If you'd prefer a separate list nonetheless, we can
    create one for bindings stuff, and I would not have a problem with
    subscribing to it. Just let me know, and please also mention if you
    subscribed, in order to know whether CCs are needed or not.

  * there is a commits mailing list, but it gets *all* the commits to
    the pkg-kde repository. So, my plan is to direct commits diffs to
    kdebindings via the PTS. Ideally via the kde4bindings source
    package, but since that doesn't exist yet, I'm sending it via the
    "kdebindings" source package for now. (So, subscribe to the "cvs"
    keyword of the kdebindings package in the PTS if you'd like them. I
    do.)

  * @Torsten: when I built python-kde4 for my own use, configure.py was
    still in use.

So, in summary:

  * you have what'd be the needed information above, and if you would
    like some bits of help or else, please mail, or come by irc.

Thanks a lot!

-- 
Adeodato Simó                                     dato at net.com.org.es
Debian Developer                                  adeodato at debian.org
 
Mankind are very odd creatures: one half censure what they practice, the
other half practice what they censure; the rest always say and do as
they ought.
                -- Michel de Montaigne