[csw-maintainers] cswclassutils splitting

Ben Walton bwalton at opencsw.org
Tue Oct 12 02:59:37 CEST 2010

Hi All,

I'm just about done with the changes to the GAR recipe will see each
CAS pair of scripts be shipped in a separate package.  As discussed
(quite some time ago) on the list, this will allow changes to one
package to be released without requiring all others to be updated at
the same time.

I've chosen CSWcas-$name as the format of the individual package
names.  Examples include CSWcas-initsmf and CSWcas-pycompile.  I'm
open to better suggestions here, but I think the above is reasonable.

The CSWcswclassutils package will depend on all sub-packages for now
until such time as nothing depends on CSWcswclassutils itself.

The last remaining wrinkle is how to distribute the directory:
/var/opt/csw/cswclassutils.  It's (currently) used by 2 of the CAS
script pairs as a place to write temp files during the CAS.  In the
short term, it can be 'owned' by CSWcswclassutils, but going forward
when dependencies are on the actual CAS required, it won't have
anything that guarantees its presence.

I see a few options for handling this:

1. Include it as part of CSWcommon.
2. Have any script that uses it do:
   [ -d /var/opt/csw/cswclassutils ] || mkdir -p /var/opt/csw/cswclassutils
3. Have the same action as above, but put it in a postinstall script
   for any package requiring the directory.

I personally favour option 2, but would like to hear what others think.

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

More information about the maintainers mailing list