Tom Mueller wrote:
I was assuming "send-uuid" would be one of the policies that would be on
the list of properties that become policies. Is that not the case?
Maybe it would help I saw the list first.
How about "flush-content-cache-on-success"? Will that be on the list of
polices?
As I said before, I'll update the proposal to include a list of
properties that should probably become policies. Even then, I
anticipate that not all policies should be allowed to be publisher
specific, so I'll add a note about that as well.
The advantage to me of separating properties and policies is that
properties, in my view, are attributes of the image only (such as
description, title, etc. that you mentioned previously; though I should
be clear that this proposal does not suggest adding those).
While policies are general behaviour settings of the system. I feel
like it is somehow beneficial, at least from a documentation and/or user
experience perspective, to clearly delineate the two.
Currently, internally there is an image.get_policy method that uses the
values of properties. I'm curious what happens to that method with this
design. (But that may just be an internal design detail).
That's an internal design detail. I probably shouldn't have gone to the
level of detail that I did in describing code changes and just stuck to
the architecture.
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
