On 13:18 01 Feb 2002, Peder Stray <[EMAIL PROTECTED]> wrote: | Dan Espen <[EMAIL PROTECTED]> writes: | > Is there a reason you don't want to put the global stuff in | > FVWM_DATADIR? | | up to seven differen flavours of unix, spred over 2-3 different | locations. i would think it would be nicer to keep our sitewide setup | seperate from files installed by fvwm.
Any reason not to use a symlink for this? Example: at work we have a sitewide apache build installed (through magic) in /opt/apache. But naturally an individual server has its own config and logs. The build-from-source was done with "--prefix=/opt/apache-1.3.23", and so the daemon believes its configs are in /opt/apache-1.3.23/conf and so forth. But post install I moved the conf dir to conf-dist and make conf a symlink to /var/apache/conf. On machines actauually running apache one then makes /var/apache and copies conf-dist into the conf subdir and customises. Similarly for your setup you would have the config stuff (architecture independent) symlinked to a central spot. Would this not work? -- Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/ I've seen things you people wouldn't believe. Attack ships on fire off the shoulder of Orion. I've watched C-beams glitter in the dark near the Tannhauser Gate. All these memories will be lost in time, like tears in rain. - Roy Baty, _Blade Runner_ -- 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]
