Cask Lingon-X vs Lingon-Pro

[jcobleigh]

Output of brew config

$ brew config
HOMEBREW_VERSION: 5.0.8
ORIGIN: https://github.com/Homebrew/brew
HEAD: b473452cf25e5f70522229d1472948584b74736b
Last commit: 6 days ago
Branch: stable
Core tap JSON: 04 Jan 17:39 UTC
Core cask tap JSON: 04 Jan 17:39 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.Ns7mVz3ae1/org.macosforge.xquartz:0
HOMEBREW_DOWNLOAD_CONCURRENCY: 16
HOMEBREW_FORBID_PACKAGES_FROM_PATHS: set
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 3.4.8 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.4.8/bin/ruby
CPU: octa-core 64-bit arm_firestorm_icestorm
Clang: 17.0.0 build 1700
Git: 2.50.1 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 26.2-arm64
CLT: 26.2.0.0.1.1764812424
Xcode: 26.2
Metal Toolchain: N/A
Rosetta 2: false

Output of brew doctor

$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: /usr/bin occurs before /opt/homebrew/bin in your PATH.
This means that system-provided programs will be used instead of those
provided by Homebrew. Consider setting your PATH so that
/opt/homebrew/bin occurs before /usr/bin. Here is a one-liner:
  echo 'export PATH="/opt/homebrew/bin:$PATH"' >> ~/.zshrc

The following tools exist at both paths:
  ctags

Description of issue

I see that the cask lingon-x is on version 9 of the App. The app has been renamed to Lingon Pro for version 10. Does this require a new cask? Should the old cask be renamed? I'm willing to try writing a cask (this would be my first time, so if someone can do this more quickly, I wouldn't say no), but not sure the best way to deal with an app being renamed.

Relevant casks

lingon-x

[andrewcrook]

Looking at the website https://www.peterborgapps.com/lingon/ the numbering system was confusing it moved from Lingon to Lingon-X this wasn't the version number and most people look at X as the roman numeral for 10. After Lingon X 9 the numbering has changed there is now a Lingon 10 on App Store (only) and Lingon Pro 10 download only from the website the latter cannot be on the App Store because it breaks Apples guidelines for some of its more powerful features. However, it is signed and notarised. Both are commercial.

So brew can only serve up to Lingon X 9 and Lingon Pro 10 not Lingon 10 leaving a gap

There is also the scenario where someone has brought Lingon-X 9 in the past not upgraded to Pro 10 and might wish to reinstall. So I would lean toward a separate cask.

Normally Brew can use aliases to point old names to a new cask this is great but cannot take into account things like licensing when tied into versioning.

Ideal world I guess you would use Lingon-X@9, Lingon-X@8 etc and Lingon-Pro@10 but I don't feel many people like this though. brew used to have a tap for different versions of casks I think its abandoned.