Design Thought for Single Machine

[Mark Sargent <ma...@diabro.jp>]

Hi All,

I'm developing a shopping system for my company with OSCommerce and will 
be constantly adding/removing code, modules etc and wanted to use SVN to 
manage the changes. I'm wondering how to approach this. I use only one 
machine for testing everything. I keep a copy of the OSC project 
separate from the  Apache htdocs copies. Should I add the copies 
directory as a new project, and do I then create another directory for 
the checked out files? I'm guessing this is so,  otherwise SVN would get 
confused, yes? Any thoughts on this? Cheers.

Mark Sargent.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Design Thought for Single Machine

[Bruce Webber <br...@fastmail.us>]

--Mark Sargent <ma...@diabro.jp> wrote:

> Hi All,
>
> I'm developing a shopping system for my company with OSCommerce and will
> be constantly adding/removing code, modules etc and wanted to use SVN to
> manage the changes. I'm wondering how to approach this. I use only one
> machine for testing everything. I keep a copy of the OSC project separate
> from the  Apache htdocs copies. Should I add the copies directory as a
> new project, and do I then create another directory for the checked out
> files? I'm guessing this is so,  otherwise SVN would get confused, yes?
> Any thoughts on this? Cheers.

You can more that one working copy for the same directory in the Subversion 
repository (i.e., project). If you want to keep a copy of the OSC project 
files separate from the files under htdocs, I would make both of them 
working copies of the same Subversion directory. Then you would commit the 
changes in your separate copy and do an update in the htdocs working copy.

Once you start using Subversion, though, you may rethink this. With 
Subversion you can create branches, create tags of significant states of 
your project (releases, for example). You can switch a working copy from 
one Subversion directory to another (from trunk to a branch, for example). 
And of course you can have multiple working copies under htdocs. This makes 
it easy to develop and test and not loose previous revisions.

-- 
Bruce Webber
brucewebber@fastmail.us
http://brucewebber.us

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org