Re: [Axiom-developer] version control

[root]

> | hmmm.... methinks you might not realize that axiom is, at least under
> | my view, trying to take a new direction about what 'source code' means.
> 
> well, so far, it has failed to convincingly tell us what that new
> direction is.
> 
> | it is my belief that systems like axiom can only survive if we start
> | writing for people rather than machines.
> 
> yes; but I don't see how that implies keeping the video under CVS or SVN.

we've had this discussion before. see the discussion surrounding your
suggestion that we make building the documentation portion of the
literate programs optional. does a checkout now exclude video?

the questions come down to 



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

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



2) what kind of environment do you expect if you want to write 
a new axiom domain? if you do:

)compile mynewfoo.pamphlet

does it build the documentation? 
does it update the browser? 
does it hyperlink to your video information?
does it allow drag-and-drop of new domains?

or does it simply extract the computer program and compile it?


t