homeworlds: update stable url

[samford]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

The existing stable URL for homeworlds is a Git revision with no tag. We have some other formulae in a similar situation but they use a commit tarball instead of checking out the Git repository (e.g., luajit), so this updates the formula to follow the same pattern.

Misread comment

[github-actions]

⚠️ Pre-merge checks failed.

[p-linnane]

What other formula are doing this? The warning in the luajit formula sounds like we should not do this.

homebrew-core/Formula/l/luajit.rb

Lines 1 to 5 in dde579e

	# NOTE: We have a policy of building only from tagged commits, but make a
	# singular exception for luajit. This exception will not be extended
	# to other formulae. See:
	# https://github.com/Homebrew/homebrew-core/pull/99580
	# TODO: Add an audit in `brew` for this. https://github.com/Homebrew/homebrew-core/pull/104765

[samford]

What other formula are doing this?

The ones I'm updating are four old formulae that have been using a specific commit with no tag since they were introduced (I found them while collecting statistics on github.com URLs):

• colortail: 0.3.4 was committed on 2012-08-01 but never tagged (see colortail: update stable url #205260 (comment)); originally added on 2015-06-07 in colortail 0.3.4 legacy-homebrew#40428
• fabric-completion: Unversioned, no tags or releases; added to homebrew/core from homebrew/completions on 2017-01-25 in https://github.com/Homebrew/homebrew-core/pull/9198/files#diff-2dfe78dbb8badfe2a0572236edf4bc9231d90259cd14eb4b40e8d582eb0b555d
• homeworlds: Unversioned, no tags or releases; added to homebrew/core from homebrew/games on 2017-02-08 in https://github.com/Homebrew/homebrew-core/pull/9685/files#diff-7949d1dfdf9cbbd742e36fc3ddb2ad8e92397fd30a7ce8a1fe324dc0667bcfa5
• pip-completion: Unversioned, no tags or releases; added to homebrew/core from homebrew/completions on 2017-01-25 in https://github.com/Homebrew/homebrew-core/pull/9198/files#diff-6348859406796f4b0ea930d70fdaba24ad5f174f747d4770e930f453ce956c40

The comment in luajit is correct but these were added years earlier and we can't use a tag in these cases. I've been updating these to use a commit tarball, as we only use Git when there's a technical need and that doesn't appear to be the case for these (they're just holdovers from years past).

In terms of existing formulae using a commit tarball, there are two more old formulae but also one that was introduced in 2024:

• runcocoa: Formula disabled, unversioned, no tags or releases; added on 2011-04-28 in 2414f22
• solid: No tags or releases; added on 2011-09-23 in New Formula: solid legacy-homebrew#7776
• wasi-libc: Formula uses commit hash of the wasi-libc submodule in wasi-sdk repository for a given tag, and that may not always correspond to a wasi-libc tag (it does right now, though); added on 2024-10-22 in wasi-libc 24 (new formula) #195222

[ZhongRuoyu]

The change looks OK to me per se since we are already using the commit so it doesn't worsen the situation. However I do think that we should deprecate this formula since it doesn't really meet our standards (and is not popular either). (Same for the other formulae mentioned in #205524 (comment) unless there's a reason not to.)

[samford]

Works for me. I've updated this to deprecate the formula.

I'm planning to open an upstream issue for colortail, to see if they will tag 0.3.4. A former Homebrew maintainer asked them to tag releases (ten years ago) and they tagged 0.3.3 but didn't go on to tag 0.3.4. It seems like they may be receptive if we ask again and that would allow us to switch the formula to a tag tarball instead of deprecating it.

I can handle the deprecation for pip-completion in the upcoming PR to update the stable URL. I'll create PRs for the others (outside of colortail and wasi-libc) afterward.

[carlocab]

Can we ask upstream if they're willing to cut a release tag before deprecating this?