[CI][Packaging] Re-synchronize conda_recipes with arrow-cpp-feedstock

[amoeba]

Describe the enhancement requested

According to #41856 (comment), we need to re-sync the recipes from https://github.com/conda-forge/arrow-cpp-feedstock into this dev/tasks/conda_recipes in order to get the nightlies building and publishing to the arrow-nightlies channel.

Component(s)

Continuous Integration, Python

[amoeba]

It looks like I could base the changes I make off of c9674bc.

Edit: #37624 is a better link

[kou]

@h-vetinari Can we create a script to automate this? For example, we have https://github.com/apache/arrow/blob/main/ci/conan/merge_upstream.sh for ci/conan/.

[h-vetinari]

The custom adaptations in the recipe should be doable to script, the adaptations in the build scripts are harder, unless there's a good way to factor out the arrow-specific bits into a hook that can just be inserted somewhere (ideally at the end).

Possible definitely, but perhaps not easy (and progressively less easy the more past 80% you want to automate).

[kou]

Thanks. It makes sense. We don't need to automate all tasks if it's not easy. If there are easy parts, we can automate them to reduce maintenance cost.

[kou]

@h-vetinari FYI: We're discussing whether we remove dev/tasks/conda-recipes or not in the dev@arrow.apache.org mailing list: https://lists.apache.org/thread/gvlvl7wx1gdkyo2lo47rgkkm3j0plvdx
If you have any opinion, could you reply to the thread?

[h-vetinari]

Seems like everyone is in favour of removing them - from my side, I could imagine maintaining those recipe, but I cannot do that for free (same as ~2 years ago).

But I actually think we don't need the test within the repo here to be able to build arrow in conda-forge. As long as maintainers here are responsive to bugs/problems, you can drop the tasks here, and have less of a hassle.