[Bug 288025] Ports version monitor does not recognize versions for kmod ports properly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288025

--- Comment #3 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to Tomoaki AOKI from comment #2)

Ahh. So (given both are for kmod packages
for the first part of the below):

575.64.1401501_2 vs. 575.64.03.1401501_1
and:
575.64.1402002_4 vs. 575.64.03.1402003_1
(I've had to take guesses at what parts
update when.)

All 4 possibly existing at the same time
as transition happen but the 1401 and 1402
text being context identifications that
should not be a mix in a comparison. So:

575.64.1402002_1 vs. 575.64.03.1401501_2

would apparently be an incoherent
comparison to make and likely should be
rejected instead of just having a true vs.
false status for one of <, =, or >, <=, >=,
or != .

Similarly, comparison of a kmod package
version string to a non-kmod package version
string looks to be an incoherent comparison
to make.

It seems that kmod package version comparison
vs. not needs to be known up front to identify
how to do the comparisons and some about when
to reject some attempts at incoherent
comparisons.


Not that is is reasonable now, but it looks
like if it had started with a more explicit
notation, it might have been simpler to deal
with. For example, starting with
575.64.00.1401501_1 so that there would have
been less structural variation:

575.64.00.1401501_1 vs. 575.64.03.1401501_2

might have helped simplify things. Optional
[sometimes-no-notation] fields in an over-time
growing sequence of fields makes field
identification and extraction messy.

It will be interesting to see how it ends
up actually being handled.

-- 
You are receiving this mail because:
You are on the CC list for the bug.