Fix a false positive in REFCOUNT_FULL in recent 5.4.x

[hlein]

Extend VersionCheck to be able to take a three-tuple, x.y.z kernel version in order to properly recognise 5.4.208 as when this became the default behavior and thus CONFIG_REFCOUNT_FULL disappeared.

Closes: #88

[a13xp0p0v]

@hlein, thanks for your pull request.

I think you need to adapt detect_kernel_version() to get the third number of the kernel version from the kconfig file.

One more aspect: you need to compare this number in the check() method of the VersionCheck class. Otherwise it will return wrong results.

[hlein]

@hlein, thanks for your pull request.

I think you need to adapt detect_kernel_version() to get the third number of the kernel version from the kconfig file.

Oh, you are probably right. I didn't have access to the box or config in question any more, so fabricated some data I was testing against; my tests must have been incomplete / accidentally-successful.

One more aspect: you need to compare this number in the check() method of the VersionCheck class. Otherwise it will return wrong results.

Oof, you're right. I think I had done things a different way before refactoring the self.ver_expected_print out, but then lost the check against self.ver_expected[2] when cleaning up. Ugh!

[a13xp0p0v]

Closing. The feature is implemented.
Please see #88 (comment).