New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve handling of caveats
for API installs
#15014
Comments
Quoting @apainintheneck (#14925 (comment)):
|
It looks like there is also at least one formula that uses Edit: This would be a one line change but do we want people to use |
Did this get fixed by adding the service block to the API? It seems like in this specific case it wasn't showing because it didn't know it was a service but now it should work fine. |
Seems reasonable to do so.
No idea, maybe! |
I just double-checked and this works fine now because the service block was added to the API. Will close this out once the one line |
Why would caveats not just use |
I think most of them do. It should be equivalent so I don't know why it can't be used instead. |
@reitermarkus and I just found out that the caveats with
|
@carlocab @apainintheneck is this now done? |
Will take a look along with a few other API issues tomorrow. Been having a look through them tonight seeing where the issues are. |
I count ~70 affected formulae, but my script is a lot simpler so maybe there are a bunch of false positives. #!/usr/bin/env brew ruby
require "formula"
require "method_source"
CoreTap.instance.formula_names.each do |name|
formula = Formula[name]
caveats_source = formula.method(:caveats).source
first_method_line = caveats_source.lines.second.strip
next if first_method_line == "nil"
next if first_method_line.start_with?("<<~")
puts name
end Formulae
|
Formulae with I do have a fix for |
Yeh, and we should probably have an audit etc. too. |
Verification
brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.Provide a detailed description of the proposed feature
Currently, you can see different
caveats
depending on whetherHOMEBREW_NO_INSTALL_FROM_API
is set or not. For example, as I mentioned in #14925,What is the motivation for the feature?
Users should see
caveats
as intended regardless of whether they install using the API or from a Git clone.How will the feature be relevant to at least 90% of Homebrew users?
90% of Homebrew users are installing, or will eventually install, from the API. They should see the same
caveats
as non-API installs.What alternatives to the feature have been considered?
Removing
caveats
? Doing nothing?The text was updated successfully, but these errors were encountered: