Just starting out - conception
From: <reader_at_newsguy.com>
Date: Thu, 03 Jan 2008 20:36:25 -0600
[ ALERT: Just to give any prospective readers a heads up.. this is
Just starting to try out svn but have been a long time cvs user.
But first understand that my cvs usage has been the most basic and
I'll try to describe the setup as briefly as I can and still try to
Over several years I've developed a three part setup.
.../cvsroot self explanatory
The way it works: I have lots of stuff on the working local
The hierarchy is a partial mirror of the os wherever the versioned
/cvsb/hostGentoo/etc/make.conf samba/smb.conf [...]
[...]
/cvsb/hostObsd/etc/ profile rc.conf inetd.conf [...]
[...]
/cvsb/genDMZ/etc/ make.conf [...]
There are 8 hosts, some no longer exist but I have kept the configs
The overall number of files isn't really very high. `find' reports 706
This has all grown up over the course of 6-8 years I guess. And been
The checked out module is a near mirror of /cvsb (the buffer)
I do it this way to avoid any permissions problems or editors not
I started out with no buffer but ran into many problems over
None of the various linux|obsd|sun x86| systems have any users but me
Any files likely to present a security risk are at least under root
All changes are carried out in /cvsb with no regard to check in/out
Things are edited as needed, or scripts written etc etc and every
About every other week I run a cvs session that starts with
and with that list, check in what needs it, Adding messages
I've followed this setup for quite a while, adding and subtracting
I've grown to like the above setup pretty well but wonder if it will
I want to switch to subversion for the learning experience but
Now wondering if I should try to maintain a similar 3 part setup with
So can some of you give me a few ideas about the initial setup. I
---------------------------------------------------------------------
|
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.