This has been bugging me since 2.1.5.
Make install puts the modules into
${PREFIX}/libexec/fvwm/${FVWMVERSION}/ now, rather than just plain old
${PREFIX}/lib/fvwm. I can understand doing this to support having
multiple versions of fvwm installed, but frankly, there doesn't appear
to be any other specific provision for multiple versions in the
install process (i.e., making ${PREFIX}/bin/fvwm2 a symlink to
fvwm2.2, etc.) So the net effect of the current install is that it
breaks .fvwm2rc each time fvwm2 is updated, since ModulePath needs to
be altered.
IMHO, it would be better to drop the version-specific target module
directory, or at least make it an option. The alternative would be to
have the module logic automatically check for a ${FVWMVERSION}
subdirectory in each directory in the module path. And please don't
suggest FvwmM4 or FvwmCPP; I don't accept that I need to run my entire
config through a preprocessor just for this.
- Jim
--
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_fwm.org.
Received on Wed Feb 24 1999 - 10:05:17 GMT