On Tue, 23 Mar 2004, Nicklas Norling wrote:
> > -----Original Message-----
> > From: Tom Vergote [mailto:firstname.lastname@example.org]
> > 1. Create a repository under the reporoot and import
> > directory's for the projects? Where would trunks and branches
> > be layed out? If I understand correctly with this setup a
> > commit in proj1 for custA would updatethe revision for all
> > projects in all customers.
> A commit is global to the repo, so yes, the revision will be increased
> for all customers and projects for each change.
> Having global revisions ticking away when there is no change feels strange
> to begin with, but one get's used to it, and it becomes very handy
> to have each change "tagged" with a revision.
So you suggest tagging everything after a change instead of relying on the
SVN revision numbers.
My problem is that a lot of our projects are web applications, and the
graphics and HTML designers need to use this source control too. They
aren't always as technical as one would hope for and i'm trying to avoid
> > 2. follow along the directory structure but create
> > repositorys in each project, and then import
> > trunk/tags/branches dir's in each projects repository.
> I'd stick with one repo. Projects and even customers may have
> stuff in common, and having them in one repo makes it easier
> to make code changes to many in one revision.
Ah, you said something i was wondering about too.
How are you supposed to (e.g.) use a dataaccess component in most of your
projects, but still have the component as a seperate project (hmm, i hope
i am clear here)
> Also proj1/trunk or trunk/proj1 that's difficult, maybe a
> matter of taste? I think I'd do proj1/trunk, seems that would be
> more isolative of the project. But it's easy enough to change
> if you decide it's not the right way to do it.
> You would want tags and branches folders in the same position
> as the trunk folder I would think.
I haven't had the change to go through the svnbook so excuse me if i'm
being ignorant, but is it really that easy to move repository's around?
For example if you have a repository per project how would one go about
moving it all into a new single huge repository.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Mar 23 15:26:01 2004