h-vetinari commented on PR #13991: URL: https://github.com/apache/arrow/pull/13991#issuecomment-1238375698
> Actually, scratch that. These files are evidently generated; moreover, the "upstream" files in the arrow-cpp feedstock are [very different](https://github.com/conda-forge/arrow-cpp-feedstock/tree/main/.ci_support). Yes, I was gonna say... These files control the "pinning" of various versions of packages whose ABI a given feedstock is exposed to. It makes little sense to try to maintain them by hand TBH. This will probably also play a part why you're pulling in outdated versions. > Given how conda-forge is maintained, perhaps it's time to admit that it makes no sense to try to maintain our own outdated versions of conda recipes in the Arrow repository? @h-vetinari @xhochy What do you think? It's not useless to run conda builds in CI here, but then you IMO shouldn't depend the .ci_support stuff. You can still pull in the compilers that conda-forge uses (well, except windows), as well as the most recent set of dependencies. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
