Ignas Anikevicius
Ignas Anikevicius
> Under the hood, each wheel/url value turns into a repo, generating a whl_library-compatible repo (i.e downloads and extracts it). The config_settings are fed into whatever generates the hub code's...
I would be +1 for (2) because it is almost doable with what we have today. For the mapping, the `(distribution ,list wheel_urls/paths, list config_settings)` I think it should work...
I like the approach 1. out of your listed ones. It should be cheap to just have: ```starlark def _linux_impl(rctx): if not _is_linux(rctx): rctx.file("BUILD.bazel", """\ toolchain( name = "linux_toolchain", toolchain...
BTW, I realized that the current hermetic toolchain understands if it is Linux GLIBC. Is it possible to detect if the interpreter is built for MUSL vs GLIBC?
Regarding `glibc`, if you look at the hermetic toolchain, we are specifying the flag value to be set to `glibc` (I haven't got to adding `musl` toolchains yet), but what...
Thanks for digging. Regarding use of packaging, it is used in all of the whl metadata parsing (and env marker eval), so using it should be OK. We could vendor...
FYI @mark-thm, feel free to write down any thoughts that you may have :)
Thanks for the comments Mark!
Interesting `uv` features: - astral-sh/uv#4524 for having local copies of the index and run unit tests to ensure particular output of `uv pip compile`. - astral-sh/uv#4505 for having a single...
Before I forget, having it a build action would make it difficult to provide extra args to e.g. pass args to uv to upgrade a single package in your lockfile....