While muddling through how to add rpmvercmp to JavaScript,
I find myself thinking Yet Again about how silly and feeble
and fragile and deficient rpmvercmp actually is.

So I ask the question:
	Can *RE patterns that match newer but not older
	packages be devised?

The general answer is boring: No, of course not.

But %track (and /usr/lib/rpm/vcheck.pl) are based
on *RE's and Get It Right! (i.e. detecting newer
upstream versions of tarballs) sufficiently often
that newer EVR comnparisons might be done with *RE's
rather than the usual slice-n-dice of alpha/digit/other
character sets and using strcmp(3).

Perhaps a better (as in easier to answer) question is
	How many types of versioning pattern templates would
	need to recognized for rpmvercmp to be done
	using *RE's instead?

73 de Jeff