On 03/21/11 06:30 PM, Danek Duvall wrote:
Shawn Walker wrote:
I think disentangling this from the preserve attribute (we can make them
play together, though) would probably be best.
Bart and I thought it best that only editable files could participate in
this scheme, hence tying it to preserve since that's what is used to
indicate that a file is editable. But perhaps I'm misunderstanding.
Tying them together is fine, but I'd use different attribute names; I think
it makes things simpler to understand.
It seemed weird to require that a package delivering a customisation for
an editable file could specify a preserve attribute and then some other
attribute that indicated that it was an override for an existing,
editable file.
So far, we've not had any action attributes that interact with each
other in this particular fashion, so it seemed simpler to make the cross
product of the behaviour visible through the values of the preserve
attribute instead of another mechanism.
However, I'm open to suggestions as to what that might look like as I
don't have a good feeling about any particular direction at the moment.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
