rattler-build icon indicating copy to clipboard operation
rattler-build copied to clipboard

extra conda package files output directory

Open trim21 opened this issue 8 months ago • 2 comments

I'm hoping to have a way to get final conda package in a seprated directory, instead of $output/$platform/$unknown-file-name.conda.

There are some use cases, for example, in CI, that users may want to collect all the conda packages and process them later in another job. In this case the conda repo is unnecessary, and it's hard to find conda packages in $output directory.

As a example, maturin by default build wheels to $target/wheels/*.whl but it has a option to copy wheels to another directory, then users can test wheels or upload them to pypi easily.

trim21 avatar Apr 07 '25 20:04 trim21

Do you have an example of what this option looks like for maturin?

I think we could potentially add an option to copy the packages to a different location but it's also quite important to have them in the structure they are so that interdependencies are correctly resolved between multiple outputs / multiple builds.

wolfv avatar May 12 '25 07:05 wolfv

https://github.com/trim21/bencode-rs/blob/78436bf21a41c2c7cea2be371f3e435d809a7c19/.github/workflows/_build_wheels.yaml#L67-L79

It's called --out, but we already have --output at rattler-build so I don't think that's a good name for rattler-build.

maybe --artifacts-path

trim21 avatar May 12 '25 09:05 trim21