Answer from Raymond Toy:
---------------------------------------
> Hello,
>
> creating a new Maxima package should work as follows:
>
> 1) Download sources from CVS.
> 2) Change line with "AM_INIT_AUTOMAKE" in maxima/configure.in appropriately.
> 3) Run "sh bootstrap".
>
> Basically it works, however the bootstrap script:
>
> #!/bin/sh
> set -x
> aclocal
> automake --add-missing --copy
> autoconf
>
> doesn't seem to do a complete job, since now on the user side (when
> installing the new maxima-package) autoconf is required (to pick up
> a changed version number from step 2).
>
>
It's not clear from what you describe, but aren't you supposed to then
run configure after bootstrap?
---------------------------------------
My problem is that I re-distribute Maxima: I needed an update from version 5.17.1,
so I created version 5.17.1.1, and for this I want to create a package which
replaces (in my re-distribution) the usual Maxima package.
How are Maxima packages created? I must miss some step.
Applying "configure" should be done by the user, not me as the package
creator.
(As I said, it's nearly working, except that now automake is needed for the user
of my Maxima-package, which is otherwise not the case.)
Oliver