Peter wrote regarding 'Re: [PIC] CVS for PIC development' on Sat, Jan 14 at 03:27:
> Something that turned me off subversion, though I can't say I researched
> it very thoughly, was that I've been told it really needs to have a
> seperate repository for each project to work properly.

For some definitions of "properly".  Subversion increments version
numbers repository-wide.  Some people find this to be a problem, but
some people will complain about anything. :)  If you want discrete
version numbers per-project, you'll need discrete repositories
per-project.  If you can look at the respotiry's version numbers as an
internal piece of data without much external significance, you'll be
fine with one repos.

> In my case I
> really would like to use the system I use in cvs, which is to have my
> repository in my data directory and check out projects into that data
> directory. This data directory then is synched to my server and work
> computers. cvs is used in the file mode, no server.
> 
> Will subversion work in such a situation? I thought it needed an Apache
> server to work, IE you can just set a random directory to be your
> repository.

It sounds like you're basically looking for RCS, not CVS (which is
little more than an RCS wrapper).  SVN can run as an Apache server
module or as a stand alone pserver-like server.  I've never used the
file mode, but it's supposedly an option. :)

For a bunch of small projects, I'd set up a single SVN repository and
then just add directories to the SVN server.  Basically, treat it as a
version-controlled backup server.  Actually, that's what I do - since
you don't *have* to check out the root level of a repository, you just
use subdirectories and check those out as appropriate.  Set up another
machine to check the root out periodically and you have an automatic
backup (albeit w/ lost version info).

--Danny
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist