[csw-maintainers] addition to CSWcommon?

[Peter Bonivart]

On Wed, Dec 15, 2010 at 6:03 PM, Ben Walton <bwalton at opencsw.org> wrote:
> I'm bootstrapping a new box (the first in a long time) and I just
> discovered that /etc/opt/csw/init.d is not created by anything (in an
> early set of packages), which breaks the install of CSWossh.  I think
> this directory would be a good candidate for inclusion in CSWcommon.
> The alternate is having it provided by each package that uses it...

This was discovered earlier, I think it was CSWnrpe that broke that time:

>On Thu, Jul 8, 2010 at 12:18 PM, Maciej (Matchek) Blizinski
><maciej at opencsw.org> wrote:
>> I thought that the way it works is that either every package provides
>> its own /etc/opt/csw/init.d, or that CSWcommon provides it.  Right
>> now, it looks like none of that is true, so I don't know how this
>> could ever work.
>>
>> Can the elders shed any light on the issue?
>
>This never happened before because cswclassutils have always provided
>a sample init file to /etc/opt/csw/init.d. With the latest flipflop
>regarding NFS the sample was moved to /opt/csw/etc/init.d in May. Thus
>nothing creates the /etc/opt/csw/init.d directory any more.

/peter