In Stephen's comments on attributes and tagging he mentions: > 14. Icons. I'll need more use cases/justification of why these need > to be actions. (How would you identify different icon sizes and > types?) My preference is to make this kind of information a URL > tag/attribute, and move responsibility to the client. (Since > every published file has a URL, that's not as big a deal as it might > appear...)
Could somebody clarify the last two sentences? Is the proposal to support a tag/attribute value that is a URL to a file that's in the package? I think that's a great idea. A concrete example of what that would look like would help. For example would it be like: add file ... path="foobar/doc/CHANGELIST.txt" add set name=my.changelist value="foobar/doc/CHANGELIST.txt" Or (gulp) this: add file ... path="foobar/doc/CHANGELIST.txt" add set name=my.changelist set value="file/0/<hashval of CHANGELIST.txt>" The later doesn't seem very useful since you don't know the URL at package publish time. For the former, does the client API provide a convenient way to get the contents of a file before a package is installed? Or at least a way to convert a file "path" into a URL into the repo? Thanks, Joe _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
