On Tue, 22 Jan 2002, Chad Austin wrote:
> Okay, I guess the question now is... where should the CVS organization doc go?
> :)
in the FAQ on the web site? I think all the docs should go there... the
only bad thing is we don't get revision control on it, but it is a nicely
managed FAQ area...
>
> And instead of |cvs co projects|, people could always do |cvs co
> projects/myproject|
>
this is true...
basically it was to make it easier to get a project (not as much typing).
also having an aki module makes more sense than having a project module
that aki is within - sinse aki is standalone. The lib module is
different, since each project would depend on it, it would be easiest to
put all common code there.
I think organizing the repos for aesthetics might not be right, it isn't a
directory structure, it is a collection of modules. (this isn't really a
strong argument though..)
The only hangup I have is that viewing the cvs source might become harder
- but is this a good reason to have one module with all projects a part of
it?
kevin
> > I think the current state is that the stuff in projects is getting moved
> > to root, and the xdl dir is getting removed (because it is in the lib
> > dir).
> >
> > ben and i were discussing this, and decided it would be annoying to check
> > out the projects module and get everyone's project at once...
> >
> > > We need a document that describes where things go in CVS. I'm very much
> > > confused. And as we all know, confusion means something should be written
> > > down. :)
>
--
@--@---@---@----@-----@------@------@-----@----@---@---@--@
Kevin Meinert __ _ __
http://www.vrac.iastate.edu/~kevn \ || \| \ / `
Virtual Reality Applications Center \ ||.-'|--\\
Howe Hall, Iowa State University, Ames Iowa \|| \| \`__,
-----------------------------------------------------------
|
