I don't just want to move the location for the sake of moving it. The disk layout of end system that will be using FVWM is unknown to me. I have no knowledge of their filesystem layout and directory structure. I need to prepare FVWM so that wherever they want to place it on their disk, it will work as long as they have the environment variable $FVWM_ROOT pointed at the place they copied it to. They will not have a compiler on their system to rebuild based on their location choice.
-----Original Message----- From: Mikhael Goikhman [mailto:[EMAIL PROTECTED] Sent: Friday, July 16, 2004 3:11 PM To: Moore, Garron Cc: FVWM Users Subject: Re: FVWM: Changing FVWM's location On 16 Jul 2004 14:17:55 -0700, Moore, Garron wrote: > > And then I would like to be able to run fvwm by doing > /newfolder/othernewfolder/fvwm/bin/fvwm > Is this possible? The instructions for doing this properly are in another message. > Is there a way to move the fvwm folder and still have it function? If the intention is to freely mv it to a location different from the one configured on the "./configure" step, then the answer is no, this is unsupported. You will have different things broken, and although it is possible to fix them one by one, I highly discourage you from doing this. Please use the proper installation procedure every time you want to relocate fvwm, you don't really need to disappoint your users by breaking things. I can think about at least 3 different reasons some modules will stop to work, ModulePath is just one of them. It is both faster and easier to repeat the "./configure; make" procedure than to manually fix all problems the inappropriate "mv" introduces. 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 [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
