%% Jim Nicholson <jim_at_osiris.kosmic.org> writes:
jn> This has been bugging me since 2.1.5.
jn> Make install puts the modules into
jn> ${PREFIX}/libexec/fvwm/${FVWMVERSION}/ now, rather than just plain old
jn> ${PREFIX}/lib/fvwm. I can understand doing this to support having
jn> multiple versions of fvwm installed, but frankly, there doesn't appear
jn> to be any other specific provision for multiple versions in the
jn> install process (i.e., making ${PREFIX}/bin/fvwm2 a symlink to
jn> fvwm2.2, etc.) So the net effect of the current install is that it
jn> breaks .fvwm2rc each time fvwm2 is updated, since ModulePath needs to
jn> be altered.
No, it doesn't; I fixed this. From NEWS:
Changes in beta release 2.1.4 (December 1998)
* Fvwm creates an environment variable FVWM_MODULEDIR containing the path
to the default module directory, for use in config files, etc.
Also, in the man page under ModulePath:
ModulePath
Specifies a colon separated list of paths for fvwm to search when
looking for a module to load. Individual directories do not need
trailing slashes. Environment variables can be used here as well
(i.e. $HOME or ${HOME}). The builtin module path is available
via the environment variable $FVWM_MODULEDIR.
The _RIGHT_ answer is twofold:
1) If you don't need to add extra entries to the ModulePath, then
_don't_ put it in your ~/.fvwm2rc file at all. Just let the builtin
path be used. I think (hope!) we changed the system rc examples to
remove the ModulePath setting.
2) If you _DO_ need to add extra entries to the ModulePath, then use
the $FVWM_MODULEDIR env. var. to represent the default path.
jn> suggest FvwmM4 or FvwmCPP; I don't accept that I need to run my entire
jn> config through a preprocessor just for this.
You don't; env. vars. are expanded in ModulePath by fvwm itself.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith_at_baynetworks.com> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
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:38:31 GMT