[Maxima] maxima 5.14.0 release candidate 1
robert.dodier at gmail.com
Tue Dec 4 09:39:15 CST 2007
On 12/4/07, Jaime Villate <villate at fe.up.pt> wrote:
> Sure, "sh bootstrap; ./configure; make; make install" works fine, THE
> FIRST TIME. However, you are left with a broken system:
>From what you have described, I'm guessing that one step in the
html + category stuff has failed, namely it is supposed to create
a temporary working directory, do all the work there, and copy the
html files back to doc/info (and not the modified .texi files).
If modified .texi files have appeared in your doc/info directory,
something has gone wrong.
What effect does "mktemp -d /tmp/foo-XXXXXX" have on your system?
> It would be better if the anchors used by the category system were
> already present in the CVS repository and not added during installation;
I dunno. I don't really see the point to that. Authors should be able
to work directly in terms of @category, just as they work with other
concepts such as @chapter, instead of low-level stuff like @anchor.
I wrote scripts instead of modifying texinfo and/or texi2html,
but it would probably be best to modify those programs instead
of running external scripts. Then there wouldn't be any question of
@anchor or other cruft.
> they should be unique and not repeated.
I'll change the scripts to smash some additional distinguishing
datum into the anchors.
> If the python script can only be run during the installation, it could
> probably create new files with the meta-data needed by the categories
> system, rather than modifying files which were retrieved from the repository.
If modified files have appeared in your CVS directory,
the category scripts are not working correctly.
More information about the Maxima