Steve Kargl wrote:
> On Fri, Mar 03, 2006 at 10:53:15PM +0100, Ryan Schmidt wrote:
>> On Mar 3, 2006, at 21:29, Steve Kargl wrote:
>>> I am considering the conversion of several of my projects
>>> under CVS control to SVN. With CVS, I set the CVSROOT
>>> environmental variable to /long/path/to/my/directory/CVS.
>>> Under CVSROOT, I have project A, B, C, and D. To work
>>> on project B, I often move into the $HOME/prj directory
>>> and issue the CVS command "cvs checkout B". This command
>>> will automatically look in CVSROOT for project B. Is
>>> there an equivalent to CVSROOT in subversion?
>>> I would like to do
>>> mkdir $HOME/path/to/SVN
>>> setenv SVNROOT $HOME/path/to/SVN
>>> svnadmin create A
>>> where A shows up in $HOME/path/to/SVN.
>> Subversion doesn't have any such support built-in, but you can do it
>> yourself on the shell.
>> export S=$HOME/path/to/SVN
>> mkdir $S
>> svnadmin create $S/A
>> cd $HOME/prj
>> svn checkout $S/A
> Having to explicitly give an environmental variable on the
> command line for each svn command, kind of defeats the whole
> purpose of such variables.
I disagree. You could theoretically have different variables pointing
to different repositories with various working copies on your computer.
For example - I have 3 separate working copies attached to 3 separate
repositories. The first is our code server, the second is a completely
separate repository for documents, and the third is my own personal code
server that I have hosted from home. SO - in the CVS world, what would
I set my CVSROOT to? Given Ryan's response, I could create
$CODE/project/path, $DOCS/project/path, and $HOME/project/path.
Received on Fri Mar 3 23:31:17 2006