On 01 Feb 2002 12:42:24 +0100, Peder Stray wrote:
>
> Mikhael Goikhman <[EMAIL PROTECTED]> writes:
>
> > Still you didn't described an example where this would be required.
> > I can invent artificial examples, but I want to see a real-life one
> > where using FVWM_DATADIR for system stuff and FVWM_USERDIR for
> > user's is not enough.
>
> we (that is Institute for Informatics, University of Oslo, Norway)
> have sitewide fvwm setup for all new users. Installed on at least 2
> different architectures as of now... using a highly modularised setup,
> where users can customize parts of the setup by making their own files
> in FVWM_USERDIR, these would otherwise be included from the global
> setup directory (same for all architectures). Other stuff from the
> fvwm distribution would be included from FVWM_DATADIR.
So you don't need more than one directory in IncludePath like I expected.
You want the situation #1:
* The system stuff in /usr/share/fvwm-includes that is not FVWM_DATADIR
* Have this command in user or system fvwmrc:
IncludePath /usr/share/fvwm-includes
I suggest the situation #2:
* The system stuff in FVWM_DATADIR, i.e. `fvwm-config --fvwm-datadir`
(by default datadir is a shared directory)
For me (and probably for you) #2 is preferable, because it does not
require to add a hard coded path to configs.
My point is that if even fvwm-themes (pretty modular and fully
configurable setup) does not require IncludePath, maybe it is not needed.
Regards,
Mikhael.
--
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]
