Never mind - I see it now in one of your previous responses to this thread.
It would seem that the only three options for an icon are: 1. Include it in the manifest. Binary content would require the use of some sort of text encoding for the bits. Has the disadvantage of making the manifest too large. 2. Include it as a file with the manifest having a pointer the file. Has the problem that the icon has to be downloaded as a separate filelist transaction to the server. Also, where do you put the file when the package hasn't been installed yet? (could be a cache within the IPS meta data area). 3. Use a set action with the attribute value being a URL that points to the icon. This requires a separate server and has the same download issue as #2. It would seem that these three options would be available for any data the describes the package that one wants to display to the user before the package is installed. Are there any other options? Tom Tom Mueller (pkg-discuss) wrote: > Can you please provide a reference to this previous e-mail? I google'd > the pkg-discuss archive and wasn't able to locate that discusion. > > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
