This thread
https://www.redhat.com/archives/fedora-devel-list/2007-November/
msg02178.html
(which is deranged and silly) reminds me of the parallel case
sensitivity issue
with rpm tag names.
Originally, rpm tag names were case sensitive, just like any unix
input typically is.
But SuSE decided (likely because of the German language) that
their version of rpm would capitalize the first letter of all tag names.
So rpm tag names became case insensitive on input, and a canonical
representation with first letter capitalized, and other letters lower-
case,
was chosen everywhere that rpm displays tag names.
Now its time to define a canonical representation for arbitrary tag
names, whose
numerical value will be derived from whatever string is chosen using
a SHA-1
digest and some additional bit twiddles.
So I ask:
Is "Arbitrary" an adequate canonical representation for an
otherwise
case insensitive input string used in a spec file such as
Arbitrary: whatever you want
or should rpm interpret the following as different tags
arbitrary:
ARBITRARY:
Note that there are encoding and possibly excluded character (':'
and white space are certainly excluded) issues present in choosing the
canonical string representation of an arbitrary tag name as well.
What say ye?
(aside) Anyone have a pointer to a "standard" UUID transform for
strings?
73 de Jeff
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List [email protected]
