`file_name` runtime bug in v1 spec conda-forge feedstock

[jeremyleung521]

Hi!

When I tried to run a feedstock using v1 spec recipe for conda-forge feedstocks, the file_name keyword (example) is actually preventing pip from finding the source files (example). It is reproducible locally on different feedstocks (mdtraj-feedstock, westpa-feedstock) and removing that option from the yaml config solves the problem. @wolfv mentioned on Zulipchat that it's because the file is not untarred when there is a file_name with a .tar.gz but it is untarred when that option absent. This is counterintuitive and wasn't the case in v0.

It would be great if it's clarified/reversed or (at least) if a warning is emitted.

Thanks!

[wolfv]

Hi @jeremyleung521 - can you elaborate the use case you have for file_name? If you want the files in a different directory, you can use the target_directory key.

[jeremyleung521]

Hi @jeremyleung521 - can you elaborate the use case you have for file_name? If you want the files in a different directory, you can use the target_directory key.

This is something before my time as a maintainer, but I think it's mostly a leftover from when it was a necessary field. I'm happy to remove it (which doesn't change anything), but it's just odd that it's not behaving as it should (i.e. same as previous behavior; being explicit with the default shouldn't modify behavior).

Here's the doc about the option: https://docs.conda.io/projects/conda-build/en/stable/resources/define-metadata.html#filename

[wolfv]

Yeah, we can add that more clearly to the docs ...