Earlier detection of core incompatibilities

[Eric Pettersen]

It would be a significant enhancement if the Tool Shed could detect incompatibilities with the ChimeraX core version earlier than actual installation, which produces a traceback and a bug report (e.g. ticket #1418). A stopgap would to make the dependency shown on the ToolShed page more obvious or emphatic than the current "Works with ChimeraX (==0.6)".

--Eric

[Conrad Huang]

In the GUI, after downloading the wheel, ChimeraX now checks for version compatibility and simply saves the file if the wheel cannot be installed. The check is not made if toolshed is invoked from the command line. Should it? (If a user says try to install this wheel file, should we try to install it?)

[Eric Pettersen]

I assume the user gets some kind of message about the incompatibility and what possibly to do about it?

As for the from-command-line installation, I'm agnostic about what happens there.

[Conrad Huang]

In the GUI, users are notified via dialog that the bundle cannot be installed. There are no options on how to handle it, since we do not know what to do. The location of the downloaded file is shown in the log.

As things currently stand, users can actually force installation by using the "toolshed install filename" command to see what errors would result if we tried to install the bundle.