-
-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
aws-sso-util: fix build without dependency on cmake or rust #118910
Conversation
# Use poetry_core backend to avoid unnecessary cmake and rust build dependencies. | ||
# Remove when release uses aws-error-utils>=2.6. | ||
# Backport of https://github.com/benkehoe/aws-error-utils/commit/f23a4bb8703e8ffabf1d008e04495572cc12d4ee | ||
patch :DATA |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One demerit is patch may break brew bump
logic.
Other options are:
- Add
cmake
(and keeprust
) dependency. Demerit is these are probably unnecessary. - Use
poetry
as dependency and manually run build command. Demerit is that we cannot usevirtualenv_install_with_resources
DSL which makes it harder to maintain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
link to that PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we should also file a PR to update aws-sso-util
to use aws-error-utils>=2.6
I see, it is just not released yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
brew bump
seems to be the easiest to deal with if it breaks.
brew install --build-from-source <formula>
, where<formula>
is the name of the formula you're submitting?brew test <formula>
, where<formula>
is the name of the formula you're submitting?brew audit --strict <formula>
(after doingbrew install --build-from-source <formula>
)? If this is a new formula, does it passbrew audit --new <formula>
?