[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Best practice for a repository of subversioned directory

From: LMC <luison_at_gmail.com>
Date: Wed, 10 Jun 2009 10:11:12 +0200

Hi all. We've been happily using subversion for a while for our projects.

We currently manage a multi-site installation of Wordpress which we maintain
via a subversion conection to Wordpress and a some 20 external connections
to repositories of themes and plugins.

Our challenge now is to build our own repository so once we have updated and
tested our local working copy we can add it to our own repository in a sort
of form of tags type WP271.a /WP271.b, etc- By doing this we can subscribe
our different sites to our different updated and tested version with our own
config, plugins, etc without having to do all of them at the same time.

The questions is that ideally we would like to maintain revision control in
that new repository. If we "export" our external working copy and then
"import" it to our own repository either in the trunk or in a tag we are not
100% sure we would loose this and all would just be considered new files.

Is it any alternative better method for this?
Can we just "export" from our external repository directly into our "trunk"
working copy of our own repository and even so maintain version control?

Thanks in advance for any help, links or comments.

Jose Luis


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-10 10:14:01 CEST

This is an archived mail posted to the Subversion Users mailing list.