Jake Colman <[EMAIL PROTECTED]> writes: > > So by simply pointing at the version to be executed, it will find any > subordinate files that it needs? It knows whih libexec to look in?
The ModulePath gets built into the executable. So it knows where to find modules. There are a few pieces of Fvwm that are obtained thru your PATH like FvwmCommand. I often run multiple versions of Fvwm, I use a shell to pick the right version, and the SHELL puts the version of Fvwm being used at the front of the PATH. > >>>>> "MG" == Mikhael Goikhman <[EMAIL PROTECTED]> writes: > > MG> On 17 May 2003 22:37:05 -0400, Jake Colman wrote: > >> > >> I recently installed 2.4.15. I'm curious to see the latest unstable > >> release 2.5.x. Can both be installed simulataneously without harm? > >> How? > > MG> Say, I have several fvwm source dirs (all from cvs branches) and sever > al > MG> fvwm installations. The current 2.5.x cvs tree is configured as: > > MG> ./configure --prefix /opt/fvwm > > MG> 2.4.x tree: > > MG> ./configure --prefix /opt/fvwm-2.4 > > MG> 2.2.x tree: > > MG> ./configure --prefix /opt/fvwm-2.2 > > MG> The executable to run is /opt/fvwm/bin/fvwm and so on. > > MG> Regards, > MG> Mikhael. > > -- > Jake Colman -- Dan Espen E-mail: [EMAIL PROTECTED] -- 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]
