Jacob Morzinski <[EMAIL PROTECTED]> writes: > Hello, > > I've just installed fvwm2.4 at my site, and wanted to send you a > report on my experience. The report has turned out to be rather > long -- you can read it or not, as you please. By the end I > explain why I think I can't afford to replace v2.2 with v2.4. > (I'm installing v2.4 alongside 2.2.)
At my site, I install every Fvwm release in a directory that includes the release number. The only copy of Fvwm in the users path is a shell that adds Fvwm to the users path, picks the release to run, and then invokes Fvwm. For the 2.4 installation, the shell noticed that the user had no .fvwm/.fvwm2rc, had a .fvwm2rc and ran fvwm24_convert. fvwm24_convert will take care of those error messages. I had a few site specific issues that fvwm24_convert didn't deal with and slightly modified fvwm24_convert before using it. Another thing the shell does is detect first use of a new release and send email to the user about the features. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: [EMAIL PROTECTED] Piscataway, NJ 08854 Phone: (732) 699-5570 -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
