Re: [Axiom-mail] Re: noweb

[root]

> It stands in my way for having a more structured build system.
> 
> When in the cyle design-code-build-test; I don't need all those dvi
> that document insist on building.  I have configure generate my
> Makefiles, but document want to generate its own.
> 
> document was a necessary step to get Axiom to the state where it is
> now.  But now, it either has to give the way or mutate significantly.
> Most of the functionalities offered by document are superceded in my
> work. So, unless, it mutates and offers me something I need and I don't
> have now, it must be retired.

eh? again i'm confused.

'document' is like 'tar', it handles a pamphlet file format with options
just like 'tar' handles gzip files.

'document' is intended to be the primary command used throughout axiom
to manipulate pamphlets, including drag-and-drop. it also handles 
issues of "NOISE" which is a top-level make function. if you say

   make NOISE=

you will see all of the latex output. without the NOISE= it will
not output the latex. the makefiles don't need to know how to
suppress noise.

there is no reason that the makefiles need to know about the
command sequences necessary to translate pamphlet files just like
there is no reason that makefiles need to know how to gunzip tar files.

why would a single command which centralizes all of the knowledge
of how to translate a pamphlet to tex, dvi, pdf, spad, etc be an issue?

lost, perhaps in limbo,

Tim
The Monty Python Wizard