Are there any gotchas in adding symbolic links to a CVS repository
file structure? I'm trying to set up cvs for Java development, and
I'd like a structure like the following:
REPOSITORY:
core/com/purpletech/util/
Utils.java,v
projects/NiceApplet/
NiceApplet.java,v
@com/ -> symbolic link to core/com
projects/NiceServlet/
NiceServlet.java,v
@com/ -> symbolic link to core/com
WORKSPACE:
projects/NiceApplet/
NiceApplet.java
projects/NiceApplet/com/purpletech/util/
Utils.java
CVS/Root = "projects/NiceApplet/com/purpletech/util"
projects/NiceServlet/
NiceServlet.java
projects/NiceServlet/com/purpletech/util/
Utils.java
CVS/Root = "projects/NiceServlet/com/purpletech/util"
Will cvs freak out if the same directory/,v files are commited or
locked by users accessing them from different symbolic link
directories? (Different Root, same ,v)
(EXPLANATION:
I'd like to use symbolic links because I'm more comfortable setting up
the repository once, so that a single checkout gets all necessary
files, rather than what I'm presently doing, which is
cvs checkout projects/NiceServlet
cd NiceServlet
cvs checkout core/com
which is also fine, and I know it works, but you have to do it for
every subdirectory (I'm using several different Java packages), so it
turns into
mkdir com
cd com
mkdir purpletech
cd purpletech
cvs checkout core/com/purpletech/utils
cvs checkout core/com/purpletech/servlets
cd ..
mkdir othercompany
cd othercompany
cvs checkout othercompany/com/othercompany
which is a big pain in the neck.)
Thanks -
- Alex
http://www.jguru.com/alex/
