Update LTspice

[radeksimko]

There seems to be an SHA-mismatch with the latest version of ltspice.

Is this a candidate for version '4' + sha256 :no_check?

The URL is still pointing to version IV, but no specific minor version, so I'm not sure if version 'latest' would be the best solution here.

[vitorgalvao]

That would fail tests, as we only allow sha256 :no_check, with version 'latest'. We should either change both (since it’s a major release, there’s not that much harm), or make the version more precise.

[radeksimko]

OK, in that case I think version 'latest' will make less harm than trying to specify a particular version.

Having said that - how does actually Homebrew detects that there's a new version then? It has to download the whole binary? Even then it can't be sure...

[vitorgalvao]

You mean the main homebrew project? As far as I know, users have to submit the version updates manually, like here. In case of latest (or head, as we’d see there), it doesn’t actually auto-update — when you install something with the head version, if you want to do install a more recent version, you have to explicitly tell it to.

[radeksimko]

Ah, so basically user would have to

brew cask install ltspice --force

to do the manual update?

[alebcay]

That's correct. We're hoping to fix that with the eventual brew cask upgrade verb, which is buried under a long list of things that need to be done first at #4678.

[rolandwalker]

@radeksimko yes, although if you read the monster issue #4678, you will see we are adding support for appcasts, to be able to detect available upgrades by another route. We will shortly have appcast coverage for about one third of App-based Casks.