Sorry, another question to ask..
As part of what I asked earlier, we are trying to
figure out the best directory structure for our CVS
projects. I am more concerned with the development
structure as I am a developer. But in general my
question is, how have some of you structured your
corporate cvs
At 11:36 AM 5/13/02 -0500, Joi Ellis wrote:
>On Sun, 12 May 2002, Ray Tayek wrote:
>
> > hi, new to cvs (used to rcs), trying to grok a rational tree structure for
> > cvs. seems like packages hang out in com.foo.packageName.
> > but this would scatter/duplicate the stuff from com.foo in many
On Sun, 12 May 2002, Ray Tayek wrote:
> hi, new to cvs (used to rcs), trying to grok a rational tree structure for
> cvs. seems like packages hang out in com.foo.packageName... so we have a
> list of these for each project and perhaps a few odds and ends in the
> default package. so it would s
What do you mean by a project? I don't understand your setup.
Why wouldn't you simply keep
cvsroot/jroot/com/foo/product1/bar
product2/baz
tayek/product1
org/quux/product1
directory structure? (Which above won't make sense unless you look
hi, new to cvs (used to rcs), trying to grok a rational tree structure for
cvs. seems like packages hang out in com.foo.packageName... so we have a
list of these for each project and perhaps a few odds and ends in the
default package. so it would seem that cvsroot looks like:
cvsroot/
I'm working on a design document on our Version Control System (VCS) in
house. I'm personally reccomending CVS (for various reasons), but alas,
the decision is not mine.
What is really the most important (IMHO) is the directory structure of
the VCS tree. It needs to be intelligent, flexible, an
