-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
Deprecate license
#17437
Comments
I don't think this is necessary. As long as it's just deprecated, and not completely removed, there should be tests for it. |
Why keep the tests, though? Ideally (or, as I see it), it being deprecated means using casks that use it won’t blow up in your face, but auditing and testing for it will. I.e., if you’re “simply a user”, everything will work as expected, but if you’re developing at all, you should be actively informed and discouraged about something deprecated. |
That's fine, and usually how it works in software development when working with languages that support API deprecation as a feature (e.g. Java). But generally, or at least in my experience, the tests remain until the deprecated API is removed in the next major release. I'm fine with |
Sounds fair. Remove that point from the top post. |
what do you mean when you say, "Remove license from all official taps."? |
Every cask has a "Remove license from all official taps." means removing the |
So is this supposed to be a PR for both caskroom/cask and caskroom/versions repos? I'm having a little difficulty understanding how this is supposed to work under the same branch. |
These are basically three separate tasks that will have to be completed in this order:
|
There’s also casroom/eid and caskroom/fonts (the latter being the causer of the Removing stanzas is easily done with a simple script, though. Deprecating |
|
Done! Thank you, @abookyun. |
Refs #16692.
license
from core.license
documentation.license
from all official taps.The text was updated successfully, but these errors were encountered: