Wolf Vollprecht
Wolf Vollprecht
Hm, I am not a big fan of this. Would love to have the spec done for repodata.json / index.json / paths.json and all these related files. I believe @jaimergp...
From what I've heard, this is fixed with newer Artifactory versions.
Could we change these to read `PIP_BUILD_ISOLATION={enabled, disabled}` and similar (new!) env vars with sane behavior?
Would you be interested in trying your use case with `rattler-build`? It's where we are currently focusing our development efforts: http://github.com/prefix-dev/rattler-build
Yes, let's finally fix it! :)
The really relevant cep is https://github.com/conda/ceps/pull/111 with implementation already available in rattler.
I just had one shower-thought: what if we would store a map for this, and could that help with `noarch: ruby` / `noarch: php` etc. packages? It's been a long...
@isuruf we wouldn't have to introduce any new noarch types. Just move the files in the right places and the noarch-map would take care of it :) I am just...
One could imagine multiple entries, such as: ``` noarch_map: { "r_bin": "lib/r/5.0/bin", "r_lib": "lib/r/lib", } ``` and noarch packages that would have `r_bin` and `r_lib` at the root would get...
Awesome, that's great! :)