The problem isn't with the client API. It's with publishing. How is one
at build time supposed to generate a pkgsend request that looks like this:
pkgsend add set name="pkg.icon" value="130989AB341248..."
where the value is the SHA1 value for some file. It's much easier to
generate:
pkgsend add set name="pkg.icon" value="images/myicon.gif"
The client can look at the manifest to see the SHA1 hashval, and then
determine whether it has to be downloaded from that.
Tom
Shawn Walker wrote:
[email protected] wrote:
For the case where the package is installed, the desire would be to
use the icon from the local path, so you need the path value in that
case.
If you're delivering the icon as part of a package, all the other files
in that package are identified by hash. The hash helps the installer
determine whether the content of a file has changed. It won't
re-download files that are the same between one build and another.
Put another way, if you reference the icon by name in pkg.icon when
the user is just browsing packages, then there's no way to know if you
need to retrieve an updated icon or not.
If you reference the icon by hash in pkg.icon, then you can be
guaranteed that you will always be getting the most up-to-date icon.
If you need a method exposed in the client api to more easily obtain a
file's name by its hash, file an RFE.
Cheers,
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
