On Tue, Jun 24, 2008 at 10:59:38AM -0700, Joe Di Pol wrote: > For example would it be like: > > add file ... path="foobar/doc/CHANGELIST.txt" > add set name=my.changelist value="foobar/doc/CHANGELIST.txt"
You could do that, but that potentially would require a second lookup in order to retrieve the file. Assume that in the future you'd be able to get back the "my.changelist" set action of a package (or multiple packages) without having to get the entire manifest, so then you'd have to do a search to find out the hash, and then you could retrieve the file. > 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. Why don't you? Perhaps you don't know the full URL, since the hostname might change, etc, but you do know the hash, and the client can easily turn that into a URL (which might potentially point at any mirror, any authority) and retrieve the content. > 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? Given a file hash, it can retrieve it directly. Given a name, it needs to look up the hash (which may or may not be uniquely mapped to the name in the repo) and then retrieve. Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
