Partial compatibility bounds

Tooling Package Management
1

We’ve been making slow progress towards a full private registry setup…

  1. We registered our packages
  2. We tagged all of them
  3. We put some compatibility bounds on some packages

Am I right that step 3 is a terrible mistake? If I understand correctly, as soon as we add a bound on some dependency D which didn’t have a bound before, the package resolver is in an undesirable state (A@new_version is restricted appropriately, but A@old_version is compatible with all versions of D past and future)

If I’m reading things right, the recommended cure is:

  1. https://github.com/bcbi/RetroCap.jl
  2. https://github.com/JuliaRegistries/CompatHelper.jl#4-self-hosting-and-other-environments

Did I miss anything?

Cédric

2 Likes
2

Yeah RetroCap is designed to fix this exact issue.

3 Likes