There are a couple of issues with svn external... AFAIK relative svn externals (like "../../path") are only handled by SVN client >= 1.5
absolute svn externals are a pain, they have to point to anonsvn which causes several issues, e.g. svn:// blocked by firewalls. I'm not an expert though! Cheers, Benoit 2008/9/29, Pino Toscano <[EMAIL PROTECTED]>: > Hi, > >> 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 > _______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
