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

Advise sought - repository structure.

From: Ian Hobson <ian_at_ianhobson.co.uk>
Date: Mon, 26 Jan 2009 20:53:44 +0000

Hi All,

Just learning how best to use subversion.....

I'm using svn for controlling the source of a php system that now has
two users - soon to be three. I'm developing on windows, and deploying
on linux. (and the only developer).

When the system gained a second user, I started a new branch, and have
been adding fixes to both branches since. This is not really
satisfactory - and with 3 or 4 branches will become an error prone pain.

As part of the latest set of changes (extensive) I have also completed
work to move all differences into just 4 files - a .css file, a .php
file and two images. There is now a common core system. Each user has,
in addition, 4 "configuration" files.

I need the configuration files to be under version control, and private
to each user. Core files should be available to all user sites.

How should I set up the subversion repository(ies) to best support this?

Would we be best served by multiple repositories, and some method of
moving the configuration files in among the "core" files?

Ideas and suggestions welcome.




To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-27 00:30:05 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.