kdesupport rearrangement

Pino Toscano toscano.pino at tiscali.it
Mon Sep 29 15:53:02 CEST 2008


> For each main kde tree we will create a tag. For example for the current
> stable KDE release we create a tags/kdesupport-for-4.1/. Within that folder
> there are (cheap)copies of the kdesupport libraries which should be used
> for compiling the KDE 4.1 tree. For example:
> tags/kdesupport-for-4.1/phonon/    (svn cp'ed from tags/phonon/4.2.0)
> tags/kdesupport-for-4.1/strigi/    (svn cp'ed from
> tags/strigi/strigi/0.5.11) tags/kdesupport-for-4.1/qca/    (svn cp'ed from
> tags/qca/2.0.1)

Why not svn:externals to either the last stable release (tag), or /branches 
with externals to the "stable" branches?

Pino Toscano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/release-team/attachments/20080929/38d561b1/attachment.sig 

More information about the release-team mailing list