Danek,
Can you please respond to the reasons that were given previously in this thread as to why using existing actions, namely the set action will not work? If existing actions will work, then
how do we solve these problems:

1. Assuming that there is a set action with a hash code for the value, how does pkgrecv know that this value is to be interpreted as an identifier for a file? Does the set action have to be tagged with some special tag? If so, how is this different from adding a separate action? Adding a special tag to the set action would seem to be overloading the meaning of a set action.

2. Again assuming that a set action is used for icons and other file-based package meta data, where would the meta data file (the icon for example) be cached in the image? Specifially, how would the set action know that there is data (a file) to cache, and what name would it use to store that data. Would another tag be defined for this? (Bart did respond to this earlier by saying that the client could cache the data where ever it wants, but the problem with this is that different clients would not have a consistent way of accessing the cached data.)

By following this logic of using a set action for an icon, the same argument could be made that
we really did not need a license action either.  We could have just had:

set name=... value=... type=license ...

File-based package meta data seems to be sufficiently different than either package attributes (set actions) or packaging license/copyright data (license actions) to warrant
having a new action for this.

Thanks.
Tom


Danek Duvall wrote:
On Mon, Jul 27, 2009 at 11:56:46PM +0530, Rajkumar Srinivasan wrote:

     What is the opinion of the team about this issue? I would like
to implement any solution the team is proposing.

It is as it always has been.  No new actions are needed, only some support
from the publication tools to make what you want to do easier than it is
now.

Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to