command-line user is given to tap a cask does not work

[gsteemso]

At some point, Tigerbrew's ability to sync with an unidentified repository of casks when you brew update started working again. However, attempting to do anything with the formulae listed during such an update elicits a complaint that one must tap the repository first. The example command-line that is printed, which is supposed to do that very thing, does not work. First, it uses an https URL which fails because Github disabled password access years ago, and when you work out what ssh URL to use instead, you discover that there is no such repository anyway.

Some digging around revealed the existence of a repository named “homebrew/homebrew-cask”, which contains subdirectories somewhat matching the structure of those reported upon during brew update, but even after using the long form of brew tap to clone it, I could not figure out how to get Tigerbrew to see the formulae buried 3 directory levels deep within it. It's probably a moot point anyway, as every such formula I looked inside with a text editor explicitly required a far-too-modern Mac OS.

This all prompts three questions:

1. What cask repository is being reported on during brew update?
2. Is anything in that repository in fact useable by Tigerbrew?
3. If so, how do you get Tigerbrew to actually do it?

[sevan]

Is this a case of using a repository intended for use with current day homebrew? (It would be expected to fail if work at all. Platform support aside, the syntax has changed for certain things & there are new additions to methods for use in formulas)
Also, far-too-modern Mac OS? gross! :)

[gsteemso]

I have no idea what repository is being described by brew update. The contents seem to match the one I found that's too new for Tigerbrew, which raises questions about how the update mechanism can process it. (I believe it is only showing me the details because I have both HOMEBREW_VERBOSE and HOMEBREW_DEBUG set in my environment.) Perhaps it is some vestigial echo of the Git logs from upstream Homebrew being reported?

[sevan]

Maybe, I've not done much archaeology here.

[gsteemso]

While I'm very interested in the source of those diff updates which get reported, I don't know any way to investigate them. Delving into the mysteries of nested (or maybe "chained" is more accurate?) Git commands is rather solidly beyond me at this point.

If neither Sevan nor Misty has any insight, please feel free to mark this closed (or tell me to, if I'm the only one who can; I don't know how that all works).