[Pkg-kde-talk] more KDE 3.4 packaging

Pierre Habouzit pierre.habouzit@m4x.org
Sat, 26 Feb 2005 11:59:31 +0100


--nextPart123272209.9JtH6I7T2X
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

>     - Daniel had repackaged arts, kdelibs and kdebase using CDBS, and
>       Christopher picked it, so we're switching to CDBS in 3.4.
excellent news ;D
wasn't kdepim already using cdbs too ?

>     - The work is being done in svn://pkg-kde/branches/kde-3.4.0.
> There are some extra subdirs there, which I'll now explain. Most
> changes come from Christopher's people/chrsmrtn/3.4-experimental,
> only that splitted in lots of small commits. The story begins at
> r477.
>
>     - I'm kind of maintaining a list of things that need to be
> addressed in kde-3.4.0/TODO. If you have insight about any of them
> (specially the first two), please share.

what is -fvisibility btw ? (wrt to gcc topic)

>     - Daniel, since all of KDE packages are switching to CDBS, I
> believe it makes sense to maintain kde.mk in a central location in
> the repo. Currently, it's on /branches/kde-3.4.0/cdbs/kde.mk, and I
> was thinking of a svn:external to include it in other modules.
>
>       Also, since you're the one that is most used to CDBS, I'd
>       appreciate if you assist us/discuss/approve the changes we
>       introduce. Ideally, the file should be maintained in a
>       conservative way so that it can be used in all modules and
> there are no divergences, right?
I agree

>       At the moment, it's your copy plus a definition for
> DEB_PATCHDIRS (see next paragraph), a workaround for #296984, and the
> 'buildprep' target (which calls make -f admin/Makefile.common).
>
>     - There is also kde-3.4.0/common-patches, which are patches to
> the admin/ dir that can be shared across modules (since the admin dir
> is identical for all of them). I see it logical to maintain these
> patches in a central location, but I'll appreciate input wrt this.
agreed too

>       I don't know if this will sound crazy to you, but I like the
> idea of having the syms (nm output) in svn, check just after building
> and commit updates if necessary. Opinions welcome.
I guess this is a really good idea here.


Oh, and btw, for those who don't already know it, I'm in elmo mode.=20
meaning there will be one DD more in the team to help for uploads.

I hope this will mean a real implication of mine in the qt-kde team.
=2D-=20
=B7O=B7  Pierre Habouzit
=B7=B7O
OOO                                                http://www.madism.org

--nextPart123272209.9JtH6I7T2X
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCIFaWvGr7W6HudhwRAgO7AKCTwuzXPrkN/vzVwdebxTj4kTt3FQCfeJ1/
eQj9NxBfwTlfi4t4mKZOeK8=
=MOk8
-----END PGP SIGNATURE-----

--nextPart123272209.9JtH6I7T2X--