sdkman/homebrew-tap exists and seems to work. Why not advertise it on main page?

[edburns]

I am stridently anti DRY, so on macOS I try to install everything with homebrew. I notice sdkman/homebrew-tap exists and these steps gave me 5.19.0:

$ brew tap sdkman/tap
$ brew install sdkman-cli

Is this a supported installation path? If so, why not advertise it on the main page?

Personally, when I see software whose default installation mechanism is "pipe this stuff thru bash" I think it's a bit unprofessional.

If it's a supported path, I can certainly make a PR here. In any case, I'm curious.

[SvMak]

Thank you for your interest in the project, your proposal sounds good.

I'm currently working on improving the website and thought I could add this.

@marc0der Could you please confirm that we can add this installation method to the main page?

[marc0der]

Hi @edburns, unfortunately, the brew tap is not actively maintained, so we do not want to advertise this on our website. If in the future we find someone to maintain it and keep it up to date, we can put it on our installation page.

@SvMak for now let's hold off with adding it.

[marc0der]

@helpermethod moving this here in case you also want to comment.

[helpermethod]

Hi @marc0der !

The formula is actually up-to-date but needs to be tagged so that Homebrew can find the latest version.

I still plan to automate the update of the formula, and hope to do so in the coming days. There is still a bigger problem with the tap, namely that after installing a new version, you need to reinstall all installed candidates. That could be fixed, and should be fixed if we ever plan to support other package managers to install SDKMAN!, but requires a little thought (basically, the candidates folder would have to be made configurable).

So while it technically works, I wouldn't recommend using it ATM.

[helpermethod]

I've just released the most recent version (in Homebrew speak: created a tag for it).

[marc0der]

Thanks for the update, @helpermethod. Let's wait until this automated process is ready before we start plugging it on the website. wdyt?

[CyberFlameGO]

I've just released the most recent version (in Homebrew speak: created a tag for it).

I hope this is an appropriate place for this, but the most recent release 5.19.0 yields deprecation on default and version commands:

[Deprecation Notice]:
This legacy 'version' command is replaced by a native implementation
and it will be removed in a future release.
Please follow the discussion here:
https://github.com/sdkman/sdkman-cli/discussions/1332

SDKMAN 5.19.0

[marc0der]

Hi @CyberFlameGO, this means that the native extensions aren't downloaded and installed under the libexec directory. Is this something you are aware of @helpermethod?

[helpermethod]

Hi @marc0der ,

this is already fixed I just need to replace the tag.

As it turns out there has been a new config been introduced to enable the native extensions which the tap was missing.

[helpermethod]

@CyberFlameGO I've replaced the tag, everything should work now.

[CyberFlameGO]

Those commands were indeed fixed - I am confused on where my $HOME/.sdkman directory has disappeared off to though. Is it involved with the change to native?