Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 36948 - add symlink for fvwm's ModulePath in /usr/lib/fvwm/ (enhancement)
Summary: add symlink for fvwm's ModulePath in /usr/lib/fvwm/ (enhancement)
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Desktop WM Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-01 09:55 UTC by Felix Eckert
Modified: 2004-03-14 10:50 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
my example for the slightly modified ebuild (diff) (fvwm-2.5.7-r5.diff,326 bytes, text/plain)
2004-01-01 10:00 UTC, Felix Eckert
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Eckert 2004-01-01 09:55:53 UTC
for configurability reasons i would place a symlink of the ModulePath in /usr/lib/fvwm/. my suggestion is /usr/lib/fvwm/current -> /usr/lib/fvwm/${PV}.

Reproducible: Always
Steps to Reproduce:
Comment 1 Felix Eckert 2004-01-01 10:00:05 UTC
Created attachment 22959 [details]
my example for the slightly modified ebuild (diff)
Comment 2 Brandon Hale (RETIRED) gentoo-dev 2004-03-14 06:49:03 UTC
I'm usually not for Gentoo-specific "enhancments", no matter how small.
Comment 3 Thomas Eckert 2004-03-14 10:50:24 UTC
this is not an "enhancement" of the package, it just makes live _a lot easier_
if upgrading fvwm.

i'll try to explain: fvwm makes heavy use of modules and in order to find these
modules a (configurable) "ModulePath" is searched. In the default-installation and
-configuration the version-number is hardcoded (e.g. "/usr/lib/fvwm/2.4.8").
So far so good. Now it is common for most users to modify this configuration
(normally they start with a copy of the default-configuration, place it in
~/.fvwm2rc and start to modify). Unfortunatly after the next upgrade of fvwm the
ModulePath needs to be adjusted.
One could make the suggested symlink "by hand" but that would lead to a "not
portage controlled" symlink in the system. If this small diff makes it in the
users with custom-fvwm2rc-configurations (the majority i guess) would have
to modify "ModulePath" only _once_ to point to the symlink.

i've seen this symlink on SuSE and RedHat installs the modules in a directory
without the version-number in it /usr/X11R6/lib/X11/fvwm2.

what do you think?