Bart Smaalders wrote:
If you specify the icon by hash, the packagemanger is free to cache it wherever it wants, and the publishers don't need to care... and those of us using the command line won't need to download the icons at all.
Except we don't currently support file actions that are payload only as far as I know (i.e. the path attribute is a required attribute at the moment). That leaves us with a few possible solutions (that I can think of at the moment):
* enhance the file action to not require a path attribute and assume such actions are payload only (this makes publication time verification problematic and the fact that the path is treated as the key attribute difficult)
* add a new 'data' action that is specifically for informational payloads to be served by the depot server via /file/0, but are ignored by client/imageplan as they are not intended to be installed to the user's target system.
If we chose the second option, the pkg.icon attribute would then be free to reference hash names of data or file actions (as appropriate). That would also allow other, future attributes to reference informational only payloads.
Thoughts? -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
