Closed JonnyOThan closed 1 month ago
Now the question is how does CKAN behave when someone tries to update their existing install?
Yeah never mind, this doesn't work too well on the current version of CKAN. It still forces you to choose when installing, and if you picked the wrong one it doesn't report the conflict until later
To be clear - did you try with RO-only or with RO/RP-1 Express Install?
RO only, but I don't think it would be any different.
in ckan 1.34.5 (unreleased dev build), this change prompts an "update" action, and if you select it then you get:
So you'd still need to manually unselect tweakscale-redist and select tweakscalerescaled-redist (which does work).
Fresh installs still have the above problem:
FYI, HebaruSan pointed out that since AJE depends on FAR, the dependency declaration needs to be before AJE for this to work properly. I haven't yet re-tested CKAN's behavior with that change though.
Since FAR depends on tweakscale-redist, users are prompted to choose between tweakscale-redist and tweakscaleRescaled-redist when installing. Adding an explicit dependency here should remove that choice (which doesn't really matter) and prevent future problematic conflicts.