Wolf Vollprecht comments

Results 1457 comments of


                                            Wolf Vollprecht

Recipe using experimental `cache:` re-executes main build script

rattler-build's behavior is relatively straight-forward: if there is a `build.sh` or `build.bat` file, use it. All outputs (incl. the cache output) are treated equally. I would argue that it's bad...

Recipe using experimental `cache:` re-executes main build script

I am fine with removing the default altogether!

Recipe using experimental `cache:` re-executes main build script

I mean globally, single- or multi-output recipes not having a default `build.sh` behavior.

Recipe using experimental `cache:` re-executes main build script

@h-vetinari @olivier-roussel I think it would be less breaking if we change the behavior of the cache output to not use the `build.sh` by default. What do you think about...

Add `--skip-if-exists` to rattler_upload CLI

We have the `--skip-existing` flag for the upload to `prefix.dev` (just like we had in `rattler-build`). I think it would make sense to implement it for other providers as well...

Pre-existing build output directory still results in recursive copies sometimes

Maybe one solution would be to add a special file ".build-ignore" in the output directory which we would use to prevent the copy-dir function to recurse in any subdirectories. The...

Pre-existing build output directory still results in recursive copies sometimes

My initial idea would be to use an empty file. We could later extend that idea and allow globs in the `.gitignore` format, too.

Pre-existing build output directory still results in recursive copies sometimes

So e.g. whenever we create a `.pixi` or `output` folder, we would always add that empty file in there to prevent rattler-build from attempting to copy those folders ever.

Update to the latest versions of everything

@traversaro I agree, but I think that should maybe another run? This one just bumps the versions of all packages that have newer releases in rosdistro :)

Git bash on windows no longer supports `pixi shell`

I wonder if one workaround can be to use ``` pixi run bash.exe ``` That should start a bash shell inside an activated environment. Would love to hear if that...