h-vetinari commented on PR #14102: URL: https://github.com/apache/arrow/pull/14102#issuecomment-1246518048
> This `.ci_support/*.yaml` are updated with `conda smithy rerender`? Is this done with the automation bots or is this done on a periodic basis? I understand we should not do it in the arrow repo as we should just pull the upstream feedstock ones. It's possible to run this locally in principle, but it would be incomplete, because `conda smithy rerender` cares about conda-forge's CI setup (in `.azure-pipelines/*` etc.), and wouldn't correctly populate `dev/tasks/tasks.yml`. But at least the CI yamls could be generated, yes. Another option might be to use the conda-forge feedstock as a submodule (in a fork controlled by arrow) where it would be possible to: * carry a small patch along the lines of what I showed aboved in the details-tag * rebase that patch semi-regularly & update the included submodule commit here to point to that * point `dev/tasks/tasks.yml` to consume the files from within the submodule This would have slightly higher impedance for development work that needs to touch the conda recipe (i.e. part of the work would be a commit to that forked feedstock and updating the PR to point to that commit), but with the benefit that we could sync the changes that accumulated throughout the development of a new arrow version faithfully to the feedstock, and easily sync back infra updates from conda-forge the other way. -- 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]
