Advise sought - repository structure.

[Ian Hobson <ia...@ianhobson.co.uk>]

Hi,

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.

Thanks

Ian

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1050243

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].