On 07/ 9/10 11:01 AM, [email protected] wrote:
On Thu, Jul 08, 2010 at 05:59:13PM -0700, Brock Pytlik wrote:
[snip]
To me, the most compelling reason for two attributes, and the reason
that I'm going with two separate attributes is that the places where
I use the information they provide is located in two separate
places. I would need to take the single long string and parse it to
find the information I was looking for (rsa vs dsa or sha256 vs
sha512). Since there's no harm in storing the information in two
separate attributes, and it makes life easier, and in my opinion
clearer to the user, I think that's what I'll do.
Bill has given a compelling counterargument: not all combinations make
sense together. Instead of trying to parse the string, you can use it
as a key into a table of supported algorithms. You just check if the
string maps to something you know, and if so, you can have that map to a
more useful binary data structure. There are other ways to do this too;
OID -> codepoint was another example.
I don't believe further discussion is fruitful. I'll be removing
pkg.sig_hashalg and having a single long string as suggested.
Brock
-j
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
