Hi, On 02-11-2023 15:13, Andreas Tille wrote:
There is probably one remaining problem. As per file R/zzz.R[2] the function checkMatrixPackageVersion verifies that TMB is running always with the Matrix version it was built against.
Well, I suggested before to just patch that check out. Is it really doing any good? If the test suite is remotely well done, it should catch the case where rmatrix breaks the package, while enabling running it against any version that works.
Well, if you get the version tightly recorded, the migration software will refuse to migrate r-cran-matrix because it would break the version in testing. No CI is needed for that. But tight version relations are a pain, i.e. they limit apt in finding upgrade orders, so if too many packages do that, it might prevent people from upgrading their system.Do you see some automatic method to approach this which is better than simply waiting for a CI test to fail (which should happen once a r-cran-matrix package of a new Matrix version is uploaded)?
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
