Hi,
Lily's installation procedure is really a pain. It works fine, if you
install lily at home on your Linux PC, where you are the One-and-only. But
in a networking environment, where security is an issue it is causing real
trouble. Usually if you say 'make' to a software package, everything gets
build. If you say 'make install' the files, needed to run the software are
copied to some public place. This works just fine for almost every GNU
package I used so far. Lily, however, for some reason does only half of
the build if I say 'make' and for 'make install' it does the rest and
copies the files. This is problematic:
1. My build directory is on an NFS server, that is centrally administered,
backuped and can be accessed from every computer on our network. For
security reason 'root' access to the file systems are mapped to 'other'.
This means if I say 'make install' as root, files can't be created in the
build directory (my umask is 022) unless I chmod the build tree to be
world writeable. Making the build tree world writeable is not a good
option I suppose.
2. When I want to install lily, so that it is network-wide available, I
can do this, because I'm the sysadmin of our department's NFS tree. But,
again for security reasons, root access to this tree is allowed only from
one dedicated machine, and this machine appears to run Solaris. For this
reason executing programs during 'make install' and complex shell scripts
is not an option. (I want to install lily for FreeBSD, Linux and Solaris
and have to do this from the Solaris-Box).
Please don't tell me: 'fix the problem and send the diffs'. In my
experience complex make systems are a lot harder to understand to people
that have not written them, than Fortran compilers written in Teco. At
some stage I tried to add a missing library (on FreeBSD) to the lily
linker line - well, I managed it, but it was 'not so easy'.
Well, I understand, that this may be of low priority for you... But may
be, you can fix it some day.
Regards,
harti
--
harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private
[EMAIL PROTECTED], [EMAIL PROTECTED]
