I’ve tagged two of the plug-ins from Haddock CMS that are going to get affected by the changes that I’m making to the core of Haddock CMS in
http://haddock-cms.googlecode.com/svn/core/branches/remove-modules-from-core/
If you have a project that uses the branch of Haddock CMS that has the admin, database, html-tags and public-html modules in the core, e.g.
http://haddock-cms.googlecode.com/svn/core/tags/2008-08-10/
or (currently)
http://haddock-cms.googlecode.com/svn/core/trunk/
Then you might need to make references to the following tagged directories in the svn:externals properties of your projects:
http://haddock-cms.googlecode.com/svn/plug-ins/db-pages/tags/2009-01-05/
http://haddock-cms.googlecode.com/svn/plug-ins/mailing-list/tags/2009-01-05/
The trunks of these two plug-ins are not being updated at this point, so there’s no rush to change the external references. While I’m working on the core of Haddock CMS (removing cruft mainly) in a branch (see above), it does not make sense to change the trunks of any of the plug-ins to work with that branch. Except for the plug-ins that have been moved from the core.
The point is that I’m trying not to mess around with code in the trunks of the core or plug-ins, but code in the trunks cannot be relied upon not to change and production systems should reference external directories in the tags directories.
Reversing Entropy 