[csw-maintainers] [policy] files/dirs in /var/opt/csw

[Philip Brown]

On 1/4/11, Ben Walton <bwalton at opencsw.org> wrote:
> Excerpts from Philip Brown's message of Mon Jan 03 19:11:26 -0500 2011:
>
>> Just to appropriately "cross link" email threads....
>
> Ok, lets!
>
> I inadvertently found the original[1] conversation while looking for
> other old threads tonight.  The thread in February was a few messages
> and then it got picked up again later on[2].  The only mention of the
> /var/opt stuff was by James, early on.  It was never actually
> discussed beyond the initial mention.  Therefore, it was not generally
> agreed as policy at that time.[3]

what you wrote above, can be summarized as, "I found an old thread
that mentioned /var/opt, but there was no agreement about it at that
time".
That is not the same thing as "there was never any agreement by people
to disallow it".

Both the summer camp writeup you have referenced on it, and the more
general policy of "we suport shared /opt/csw ", encompass agreements
that it should not be allowed.

We have THREE board members, but we've only publically heard from one
on this issue.
I'd like to see our other two members write something about the above
two agreements, relating to this issue.
Particularly the claim of ambiguity about /var/opt/ in
http://wiki.opencsw.org/shared-opt-csw-setup

I would say it is completely clear, and you are misreading it. There's
a difference between "ambiguity" and misreading.


directory       writable  Allowable use
/var/opt/csw       Yes  Allowable for run-time-only data. Do not
deliver files in package here

That seems completely non-ambiguous. The meaning of "run-time" is non-ambiguous.
The meaning of "Do not deliver files in package here" is completely
clear in terms of disallowing files in the prototype under
/var/opt/csw.
The only ambiguity is whether it allows indirect "delivery" via
tactics such as postinstall or class action scripts.