You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 25, 2022. It is now read-only.
[…]
==> Installing Cask tm-6502-assembler
Error: wrong number of arguments (2 for 1)
Breakage like this is to be expected because Homebrew’s infrastructure currently is not designed to allow for external commands (like brew tm) to introduce new artifact types or stanzas. With the custom tmbundle stanza being a crucial feature of brew tm, I had to find another way to get this done; I ultimately managed to implement it with only a few lines of code while at the same time depending on as few Homebrew-specific implementation details as possible (i. e., Hbc::Artifact and Hbc::DSL).
Unfortunately, Homebrew’s recent PR (see above) has refactored exactly those two classes and many more.
To fix this, I think we need figure out the following things:
What has happened to the Hbc::Artifact::Base::me? method? (If I recall correctly, HBC used to call this to figure out which handler classes are responsible.)
In Hbc::DSL, what needs to be added to #artifacts[:tmbundle] to gain back the functionality?
It seems that a few days ago, parts of the Homebrew core have been refactored in a way that seems to break homebrew-textmate:
Breakage like this is to be expected because Homebrew’s infrastructure currently is not designed to allow for external commands (like
brew tm
) to introduce new artifact types or stanzas. With the customtmbundle
stanza being a crucial feature ofbrew tm
, I had to find another way to get this done; I ultimately managed to implement it with only a few lines of code while at the same time depending on as few Homebrew-specific implementation details as possible (i. e.,Hbc::Artifact
andHbc::DSL
).Unfortunately, Homebrew’s recent PR (see above) has refactored exactly those two classes and many more.
To fix this, I think we need figure out the following things:
What has happened to the
Hbc::Artifact::Base::me?
method? (If I recall correctly, HBC used to call this to figure out which handler classes are responsible.)In
Hbc::DSL
, what needs to be added to#artifacts[:tmbundle]
to gain back the functionality?@reitermarkus Can you help shed light on this?
The text was updated successfully, but these errors were encountered: