On 16 Jul 2004 16:09:35 -0700, Moore, Garron wrote:
>
> What you have explained below is not an option for us. We can't assume
> the location that they are putting it. I can't even assume that they
> have root access or write permissions in /usr/local or /opt. Given
> this, do you have any recommendations?
I can believe they have no compiler, but have no root access? Do you mean
different users should have separate fvwm installations on these machines?
Why the admins would not cooperate and install one global fvwm instance?
If anything else fails, you may still write to /tmp.
Create a wrapper script doing "ln -sf `dirname $0` /tmp/fvwm-root" before
launching bin/fvwm, and then "touch /tmp/fvwm-root" every hour until fvwm
runs if you fear some automatical process may clean up old files in /tmp.
> I would be willing to create a script that goes into any file where the
> path is stored and replaces it.
I would really like not to discuss this solution. Besides, I don't think
you can edit binary executables.
Another idea is just to ask the users about the prefix directory they
want to use for fvwm (or assume it is /home/joe for user joe) and then
build the binary package with this prefix for them. You may even fully
automate this process, they send an email with one subject line and get
the tarball as the result.
Regards,
Mikhael.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri Jul 16 2004 - 18:47:51 BST