Robert Dodier write:
> On 5/5/07, Viktor T. Toth <vttoth at vttoth.com> wrote:
>
>> On UNIX systems, I think you need to run Maxima as root once and do a
>> load(lapack), to let it do its compiling and deposit binary files in the
>> share directory (not normally writeable by non-root users.) After that, you
>> should be able to load(lapack) as a non-privileged user.
>
> Another work-around is to copy maxima/share/lapack to some
> user-writable location and then load it from there.
I strongly dislike current situation. Necessity to compile
something in user's directory or even worse - get root or
Administrator privileges it is against usual rules of
software installation and uninstallation.
We are going to receive a lot of questions and complains.
Just consider - compilation in user directory seems to be nice.
But if I want to make this compiled lapack available
for everyone? I have to get root privileges and copy
compiled data into common location.
But if I want later remove Maxima? Compiled lapack files
are not part of the installed package and root have
to clear them manually. Etc, etc, etc ..
> This problem came up a while ago. One of the ideas raised at that
> time is to compile lapack (and some other share package which have
> their own defsystem or whatever it's called) and package the binaries
> so that the user needn't compile it. The only drawback I see is that
> would increase the size of the binary package by some megabytes.
>
Is it really a lot? These files can be packaged in separate .rpm
and .deb subpackage and or as an extra option in Windows Installer.
I suggest to introduce extra configure option which will control
whether lapack will be compiled or not.
--
Vadim V. Zhytnikov
<vvzhy at mail.ru>
<vvzhy at netorn.ru>