[csw-maintainers] Adjusting $(DIRPATHS) for sparse zones support with shared /opt

[Mike Watters]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> you make this "go all the way" statement multiple times, but I dont
> understand what you mean by it.

I have to agree with Ben here, and we should "go all the way" with using
/etc/opt/csw.  what "I" mean by "go all the way" is no longer use /opt/csw/etc
or /opt/csw/$foo/etc and everything gets put in /etc/opt/csw or /etc/opt/csw/$foo

> So, if the site admin replaced it, with
> /opt/csw/etc/someglobal.conf -> /etc/opt/csw/someglobal.conf

I am not sure that is the case. the way you have it linked above...
if the admin links the version from /opt/csw/etc to /etc/opt/csw
that link would be true for every host.  if the /etc/opt/csw file does not
exist on a particular host, the config would be non-existent.

> then that symlink would be left along, and what is normally a globally
> shared config file, becomes a machine-local config file, for that site
> only.

the link would be left, as well as a someglobal.conf.CSW file
which the apps are not currently configured to use.

- --
Thanks,
Mike

"Any intelligent fool can make things bigger, more complex,
and more violent.  It takes a touch of genius -- and a lot of courage --
to move in the opposite direction."

* Albert Einstein 1879 - 1955
    US German-born Theoretical Physicist
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAko61vsACgkQLrhmsXMSLxcz4wCg0ZmdH0r239M7303r1GuaoM1J
LDAAoN9sIpiM5zpnKr9u3+3fteCw4DoM
=Hy1F
-----END PGP SIGNATURE-----