-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
Building with --features=gix-features/zlib-stock
still pulls in libz-ng-sys
#841
Comments
One workaround is to do
but it's not clear at all how much this disables relative to the default configuration. Ideally it should be simple to choose features so that they are identical to the default Another workaround is to replace Line 107 in d67551d
with
However, it would be nice to not have to hack up a For reference, this is related to Homebrew/homebrew-core#129719, where we're trying to package |
Thank you so much for reporting this and most importantly, provide a workaround. What's astonishing here is that I was not aware that it's possible to specify any features that are defined in dependencies of the crate. This makes cargo features so much more powerful! With that said, the way features are currently organized it's hard to reproduce exactly what the default is, minus zlib-ng, + zlib-stock, but being able to specify it from the command-line might be a game-changer for future iterations of how features are exposed by the crate. As for the actual issue described here, there is nothing that can be done as Maybe for now, you can maintain a patch file to make the changes directly where you need them? I will think about better ways to organize features, but can't know for sure I will manage to make significant improvements. |
In the linked PR (and soon in main) you find the improvements needed more more easily build something like gitoxide - Rust.pdf - jump right to the Thank you |
This works great, thanks!
Will this be in your next release? |
Yes, it will be, and I think it's worth waiting as it will contain |
Yes, the
Great, thanks! My only other request is for you to avoid changing these flags in future releases. We only have a small team of maintainers at Homebrew for ~6000 packages, so we rarely have the time to check updates carefully for changes to the build configuration. We often only notice that configurations need to change when packages fail loudly while building. |
I will do my best to keep them those working and won't change them lightheartedly. Fortunately it seems like these flags are stabilizing, especially after the recent push, as they seem to now fit their purpose pretty well. Besides that, it's exciting to see |
Duplicates
Current behavior 😯
Doing
from the repository root still builds
libz-ng-sys
. It also buildslibz-sys
, as requested, so it's not very clear which backend ends up being used.Expected behavior 🤔
Cargo should build only
libz-sys
, and notlibz-ng-sys
.Steps to reproduce 🕹
Run:
Instead of
cargo install
, one can also doto see that multiple backends are built.
The text was updated successfully, but these errors were encountered: