Marcel
Marcel
The `.in` extension is often used when using `pip-compile` to "compile" the `.in` to `.txt`. It should be treated as valid in https://github.com/simion/pip-upgrader/blob/87da550546d6f73a22b130de892d481dae0205f3/pip_upgrader/requirements_detector.py#L47 Currently there is no way to tell...
Currently, it only parses `WORKSPACE`: https://github.com/bazelbuild/buildtools/blob/19c62d9fc1d29ca99c3faa08f78cd90b36f49908/wspace/workspace.go#L123 This is used for example by `edit.InterpretLabel()`: https://github.com/bazelbuild/buildtools/blob/19c62d9fc1d29ca99c3faa08f78cd90b36f49908/edit/edit.go#L41-L113
The extension check causes more issues than it solves. The remaining protections are sufficient: - checking for file existance - checking mime type - checking for predefined names in auto-detect...
This aligns this to what other tools are doing. The `_join_flags_list()` pattern is also used for other foreign build tools. This is required to fix `--sysroot` flag even without cross...
See #1295 for a reproduction example. Both `configure()` and `meson()` don't seem to detect the hermetic toolchain and fail with errors like `C compiler cannot create executables`.
This does not build with the configured hermetic toolchain. # Instructions ## (Optional) Run in container Create container: ```sh docker run -it --rm -v $(pwd):/work -w /work debian:12 ``` Setup...
This is required to fix `libdav1d` in #1295.
When using the local toolchain, everything builds fine. When using the hermetic tool chain from this repo, some build systems fail to use the compiler for a simple test program....
We want to make all paths relative by using `strip_prefix = "/"`. While this works just fine with `pkg_tar`, when using `mtree_mutate()` it deletes the whole file instead of just...