Re: [Axiom-developer] version control

[root]

| > The crucial difference is the first step.  The distribution tarball
| > need not contain only source files that come from the CVS/TLA/SVN repo.

> If you want to test what the distribution should be/work then say "make
> distcheck" instead of simple "make", but you did not answer that
> question :-) 

i have no idea what a 'distcheck' could mean.

so only programming language code goes in the CVS?

what about the documentation?
what if the documentation is hyperlinked?
what if the documentation is dynamically constructed?
what if the documentation is in video?
how do you do versioning without a CVS?
how do you do coordinated development without using CVS?
WHY do coordinated development WITHOUT using CVS?

if the non-programming language files reside elsewhere
who holds these 'master files' that make up a distribution?
 
how did axiom suddenly change from a project into a 'distribution'?
what exactly is your definition of a distribution and how does it
differ from the current system?

so my answer to YOUR question is that *I* believe that the CVS is the
correct place to store the project files.... ALL the project files. 
so they can be versioned. so we can recreate the video from last year. 
so multiple people can coordinate building documentation.
so anyone can build a complete system from the CVS. 

this is why we use a code versioning system at all.
otherwise lets just put tarballs on the wiki.



> I believe I carefully answered:  I believe the steps are broken
> because the first one.

so, i repeat *MY* question. Assume the first step happens:


 1) what kind of final product do you expect when you do:

 cvs co ... axiom
 cd axiom
 ./configure
 make
 make install
 axiom

t