rajkumar wrote:
It may not make more sense to reference the file by it's SHA1 name. It
may be appropriate to reject this comment. The manifest can be used to
translate from a filename to the SHA1 name if the goal is to retrieve
the file using a /file/0 operation (for the case where the package
hasn't been installed yet). 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.
Excuse me, this makes no sense.
If I'm running the packagemanager, it would like to display the icons
specified in the packages; to do this it needs a copy of the icon,
cached locally. Packages would be published by a wide variety of users,
using a wide variety of icons; since the paths used by the package may
not exist before installation the icon would to be placed in a
consistent location in the filesystem by all packages... and the
names of those icons would have to be agreed upon by publishers.
If you specify the icon by hash, the packagemanger is free to
cache it wherever it wants, and the publishers don't need to
care... and those of us using the command line won't need to
download the icons at all.
> It would be very inconvenient to have to
> calculate the SHA1 value when constructing the manifest; this
> would make publishing too difficult.
Only if you're computing the hash by hand:
: ba...@cyber[51]; digest -a sha1 /usr/lib/libsocket.so.1
5ac03ca329325f44c793c2bd4d80443b9d16aebf
: ba...@cyber[52]; pkg search 5ac03ca329325f44c793c2bd4d80443b9d16aebf
INDEX ACTION VALUE PACKAGE
content file lib/libsocket.so.1 pkg:/[email protected]
: ba...@cyber[53];
- Bart
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
