James Amundson wrote:
> > And finally I have some specific feature request
> > which is related to rpm build/packaging system
> > (maybe to debian build system too, I just don't
> > know debian).
> >
> > Traditionally when binary rpm package
> > is built the install stage writes all package
> > files into their actual locations
> > /usr/bin, /usr/lib ... etc. This is not very nice
> > and safe thing.
>
> <snip>
>
> What you describe is certainly the Right Way. I think you can do what
> you want without any modifications to the build system. The build system
> uses the built-in features of automake wherever possible, so the maxima
> package should be a pretty ordinary package. The basic idea is to do
>
> ./configure --prefix=/foo
> make
> make prefix=/buildroot/foo install
>
> I just tried it and it worked.
>
Of course it worked. The problem is with the very
last stage. After
make prefix=/buildroot/foo install
the path /buildroot/foo remains hardwired
in maxima. At present I know _at_least_
two places:
1) /usr/bin/maxima wrapper script.
This is easy to fix - I just apply
sed to it to replace all occurrences of
/buildroot/foo by /foo.
2) Maxima internal variables (I can't recall it's long name right now)
which determines where Maxima looks for aaa.* when load(aaa);
is executed. What is the right way to handle this situation?
Well, I can imagine several tricks - extra initialization
script or command etc. But maybe we may handle it in a more
systematic fashion. Maybe maxima wrapper script should
assign prefix to some environment variable and this
setting override vale hardwired into maxima
binaries?
Vadim
--
[ Vadim V. Zhytnikov <vvzhy@mail.ru> <vvzhy@td.lpi.ac.ru> ]