[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: CVS to SVN, best practice

From: Jing Xue <jingxue_at_digizenstudio.com>
Date: 2007-04-10 17:21:17 CEST

Quoting BRM <bm_witness@yahoo.com>:

> So where my Makefile use to look like:
>
> PROJ_TCP = projTCP
> PROJ_TCP_RELEASE = PROJTCP_1_1
> ...
> sharedTCP: projTCP/
> cvs export $(PROJ_TCP) -r $(PROJ_TCP_RELEASE)
> ...
>
> I'll now have to do something like:
>
> PROJ_TCP = https://my.svn.server/projTCP/release/projTCP_1_1/
> ...
> sharedTCP: projTCP/
> svn export $(PROJ_TCP)
> ...

Why not:

SCM_ROOT = https://my.svn.server
PROJ_TCP = projTCP
PROJ_TCP_RELEASE = PROJTCP_1_1
...
sharedTCP: projTCP/
       svn export $(SCM_ROOT)/$(PROJ_TCP)/release/$(PROJ_TCP_RELEASE)

As long as you stick to whatever convention you come up with,
logically, you'd still be concerned with the same concepts as before,
namely the server (which I presume you had an implicit CVSROOT), the
project name and the target release/tag.

-- 
Jing Xue
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 10 17:24:01 2007

This is an archived mail posted to the Subversion Users mailing list.