| Summary: | add symlink for fvwm's ModulePath in /usr/lib/fvwm/ (enhancement) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Felix Eckert <dadula> |
| Component: | New packages | Assignee: | Desktop WM Team (OBSOLETE) <desktop-wm+disabled> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | CC: | eckert.thomas |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | my example for the slightly modified ebuild (diff) | ||
Created attachment 22959 [details]
my example for the slightly modified ebuild (diff)
I'm usually not for Gentoo-specific "enhancments", no matter how small. 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? |
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: