Skip to content
Prev 14576 / 15075 Next

Rebuild binaries when a LinkingTo dependency changes

That looks like an issue in TMB - is there really a problem between the two versions or is TMB just making it up? I strongly suspect the latter.
Short answer is no for most people, except TMB's own current behavior requires it (by its own design) so it depends on what the TMB maintainers really want - if they really want to insist on very specific Matrix version (for whatever reason), then yes.

The version generally doesn't matter in vast majority of cases, because packages typically don't make changes that break their reverse dependencies - which is why the check like that TMB does is generally not very helpful since it is way too conservative to the point of being uninformative. Even if you use LinkingTo, you should not be relying on internal behavior of a very specific version of a package - that's the whole point of defined API like what packages present through the LinkingTo-API - you only request a version of the API regardless of its implementation. If you use a new feature then you obviously have to bump your version and specify the the new version of your dependency so that problem doesn't arise. So there is an issue only if your dependency makes a change which breaks your own package (which is extremely rare - in the case of Matrix it is unfortunate, mostly due to issues in the S4 implementation) and then the only reliable solution is to bump your version since the two binaries are undistinguishable. The problem is that there is no automated way to do that - pretty much the dependency has to tell you or you have to find out yourself.

As I was explaining this is not about re-building - it doesn't help because it's not generally available to users as they have no way to know that they need to re-install exactly the same version of a package like TMB - unless the package bumps the version. Essentially the users would have to remove and re-install all packages every time they update a single one which is not realistic.

Cheers,
Simon