Robert Dodier writes:
>>1. Do something with internal automake variable
>>am__infodir.
>>
>>2. Don't use automake for info/es and info/pt
>>directories.
>
>
> OK, (2) seems like it will lead to pain and suffering later on.
> It seems like there must be an automake variable which
> tells the destination for the info files -- otherwise how could
> the Makefile know where to put things?
> So I would like to encourage you to pursue (1) or some variation of it.
>
OK. I'll investigate (1).
But what in you opinion is wrong with (2)?
The only trouble I see -- we have to create Makefile.in
by hands. Just more work than with Makefile.am but
not too much. It also violate nice "all automake"
scheme. Not beautiful.
> For my part, I'm not too worried about it, since automake
> problems don't affect users so long as we can create
> a valid official installation.
>
I don't share this attitude. I can't go further with
maxima.spec and Windows installer. What about distros
or individuals which want package maxima?
Rely on prebuilt binaries only? No way!
This isn't way open source software exist.
Broken configure/make/install
is blocker bug for release.
We have either to invent some work around
or postpone Spanish and Portuguese documentation
integration for next release.
Best wishes,
Vadim
--
Vadim V. Zhytnikov