From kde-multimedia  Mon Jan 17 00:34:04 2011
From: Michael Pyne <mpyne () kde ! org>
Date: Mon, 17 Jan 2011 00:34:04 +0000
To: kde-multimedia
Subject: Re: kdemultimedia and svn -> git
Message-Id: <201101161934.04794.mpyne () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-multimedia&m=129522449009705
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1890497056=="

--===============1890497056==
Content-Type: multipart/signed;
  boundary="nextPart1931065.mp1J6bDHgH";
  protocol="application/pgp-signature";
  micalg=pgp-sha256
Content-Transfer-Encoding: 7bit

--nextPart1931065.mp1J6bDHgH
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Wednesday, January 12, 2011 14:31:12 Ian Monroe wrote:
> So we should move to Git. Its what folks are doing.
>=20
> What do people think? Luckly Nicolas Alvarez that I have CCed to this
> email (PovAddict on IRC) would do most of the work involved. There
> would need to be some cmake-tweaking to make each app build on its
> own, but it should be pretty straightforward.

Well, we should go ahead and see if we can get a conclusion to this. I=20
personally would probably prefer a non-split repository. However I could=20
certainly live with a split one, and to that end I have some ideas of how a=
=20
split repo would be setup:

As a reminder, here's the directory layout we need to take care of:

    cmake/
    doc/
    dragonplayer/
    ffmpegthumbs/
    juk/
    kioslave/
        audiocd/
    kmix/
    kscd/
    libkcddb/
    libkcompactdisc/
    libkdemultimedia/
        kdemultimedia_export.h
    mplayerthumbs/
    strigi-analyzer/

The easy things are applications: JuK, KMix, Dragon Player.

On the other hand, KsCD and kio_audiocd are independent, and both use libkc=
ddb=20
and libkcompactdisc. So, I would think that those all go into a kdemultimed=
ia-
compactdisc repository. (And by all means, feel free to suggest better name=
s)

ffmpegthumbs and mplayerthumbs have similar functions (obvious from the nam=
e).=20
Take those and add strigi-analyzer and we have metadata-gathering=20
applications. So maybe clump those into kdemultimedia-filemetainfo ?

=46rom there we can leave all the rest in a "kdemultimedia" base module. I'=
m not=20
sure that git supports base modules that are not simply shells around=20
submodules (i.e. modules that have files of their own *and* submodules). Bu=
t=20
if git doesn't support that, we can work around it with=20
projects.xml+a_build_script and/or CMake magic.

Thoughts? Any other opinions from KDE Multimedia devs regarding whether to=
=20
split (and if so, how?)

Regards,
 - Michael Pyne

--nextPart1931065.mp1J6bDHgH
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iQIcBAABCAAGBQJNM458AAoJEAuvDJx7aunyL5wP/1mSdRqDrNc2fdGGqZ8DyCHa
yppyzb073ojklfTGWeBAsij/LY+CYBEukcd1pN4jW0bMN2USkCfjh3Z4W7WZsZMu
dNXUpNl+s3xyyoNfbi7J88ZR3JKzDjCiZyFL0RCBU0QDWq2aWNMt9/8EOfQ/pdj8
7HUgrpOdqr1nnkbL/4Lcs97gNCwseuvHi+39bcdy33p+YhGBL4sIhv2PMNStHFsV
RTChHZEKJovL5QNr3rZ2JBvZIM4soHVFkRRiFP1AEqqxaVuqy8zx0rdIhTY1gD6c
xg1qZEbifCSOdWIfyhZWZ+Pcm5/5lv0bsM7YCLP6e7556h1/6kotr+i9ZeSY0qw+
uE2imwVZWiOLjUGTMqINHBRr30nup9Cyxee6C3H697bYMxyy1s1ZtbSHQGwUw7N7
Ql2TBKDxnscsRH3GPeH+/9VcNBfpMnqU3NFWE5DBrFzW9EUB+BBFvENHJQkAnGBW
VRJPbCK372cExVPfZ8QsMpKPbJdwS9E2xlldSk1WnvZFHzcpAX35ZdnsxK24P8KV
d4rFWx5e9DZy+wDzMb4QRtgFbGL7RhQsmY8sZtlapu+Y+nuylGP3GQ6UB3gbI8zf
9Z0bOLRgpW5s5rWs2VHdXaEgEOCQU0cN+I1oRfE7yByt7oPZuNCbOnP3WLYP2A/b
z9S+HBBz50yS3LlChdRw
=l2S+
-----END PGP SIGNATURE-----

--nextPart1931065.mp1J6bDHgH--

--===============1890497056==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kde-multimedia mailing list
kde-multimedia@kde.org
https://mail.kde.org/mailman/listinfo/kde-multimedia

--===============1890497056==--