Tom Mueller (pkg-discuss) wrote: > 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?
Hi Tom, From what I know (maybe I am wrong) all three options requires downloading something from the server for non installed packages. If package is not installed than to get description field I need to download manifest first. The same would be for the option #1 containing icon or other encoded binary content. In such case we would probably hit problems while text encoding. More complexity is just more bugs. I would vote for second option. From the user perspective adding such information doesn't require downloading it. This might be an option just for particular cases. Let's say that icon is needed only by GUI's than those should ask IPS server for download icon action and get from proposed cache within meta data?. CLI doesn't require icons so it will stay as it is. -- best Michal _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
