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

[Ben Walton]

Excerpts from Mike Watters's message of Thu Jun 18 12:04:51 -0400 2009:
> > 1. A single /etc tree (eventually), and not including some of the sfw
> >    stuff, etc.
> a single etc tree can be accomplished with either directory

Not if you take single to mean 'all etc content'  Ultimately, I'd like
the CSW etc to be nested in the system /etc, which is my 'definition'
of single.  If you take single to mean single within CSW, then yes,
you're right.

> > 1. For people sharing out a single install (possibly per $arch) with
> >    NFS, /etc/opt/csw may make things more difficult, although I'd
> >    argue that symlinks could work around this quite easily.  [For
> >    people in this situation, would creating symlinks for you?]
> symlinks may or may not work if you are trying to run on zones from a single
> installation on a global zone.

Yes, zones certainly complicate things.  As we are zone-free here, I'd
appreciate others chiming in here.  What is the best way to handle
this wrt zones.  Does the best option for zone support help or hinder
the idea of nfs sharing as a goal?

> > 2. Potentially painful for maintainers during the transition.
> yes, but I wouldn't consider that a con per se

Fair enough.  Any change will see some short-term (or long, depending
on package update cycle) issues, I guess.  It does get tricky though
in some cases.

Hypothetically take the libxml and docbook packages.  If docbook moved
etc's first, it would still have to reference the old locations, since
libxml is rooted in the old location.  When libxml is updated, docbook
would need to be updated too, to handle the new location.

Shall we start a new thread on users@ then?  Any objections?

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20090618/c0808e47/attachment-0002.asc>