feat(mtoa-2027): add conda recipe for mtoa 2027

[andrew-fenton]

What was the problem/requirement? (What/Why)

Adding support for Maya to Arnold 2027.

What was the solution? (How)

Added maya-mtoa-2027, based on maya-mtoa-2026. Three changes are more than a version bump and worth review:

• The 2027 download is Autodesk_Maya_2027_Linux_64bit.tgz — the 2026 archive had an _ML_ infix.
• The Arnold payload ships as Packages/package.tgz in 2027 where 2026 used Packages/package.zip, so extraction changed from unzip to tar -xzf. The maya-2027 recipe makes the same change.
• patchelf is now declared in build requirements with a CondaChannels: conda-forge job parameter. build.sh has always called it, but neither 2026 nor this recipe declared it — it resolved only because the outer build environment happens to provide it.

What is the impact of this change?

New recipe only; no existing recipe changes. Note that testing this against an adaptor-based job also requires the mayapy wrapper fix in maya-2027 (#280), without which any Maya 2027 job in an environment containing the maya-openjd stack segfaults.

New recipe only; no existing recipe changes. Testing it with an adaptor-based job also needs the mayapy wrapper fix in maya-2027 (#280): without it, any Maya 2027 job whose environment also contains conda-provided Python 3.13 package segfaults (e.g. maya-openjd).

How was this change tested?

• ./submit-package-job maya-mtoa-2027 builds and publishes successfully.
• Submitted turntable_with_maya_arnold with CondaPackages="maya=2027 maya-mtoa=2027 maya-openjd=0.15.13 ffmpeg"; Arnold rendered and the job completed.

Was this change documented?

Yes. The recipe's README.md is updated for 2027, and conda_recipes/README.md gains an "Arnold for Maya 2027" row (with the table count updated).

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

build.sh calls patchelf unconditionally, but this conda-build recipe only requests maya in requirements/build — unlike the sibling recipe.yaml, which lists both maya and patchelf. If anyone ever builds via conda-build, patchelf would not be in the build environment and the script would fail at the --add-rpath line.

Note also that deadline-cloud.yaml declares only a linux-64 / rattler-build platform, so this meta.yaml is never exercised by submit-package-job. Either add - patchelf here to keep it buildable, or drop the file rather than shipping a recipe that cannot build.

[github-actions]

build.sh calls patchelf unconditionally, but this conda-build recipe only lists maya under requirements/build — unlike the sibling recipe.yaml, which lists both maya and patchelf. If anyone builds via conda-build, patchelf will not be in the build environment and the script fails at the first --add-rpath line.

Note also that deadline-cloud.yaml declares only a linux-64 / rattler-build platform, so this meta.yaml is never exercised by submit-package-job. Either add - patchelf here to keep it buildable, or omit the file rather than shipping a recipe that cannot build.

[github-actions]

The about block describes Maya, not Arnold — it was carried over verbatim from maya-2027/maya-mtoa-2026 rather than adapted for this package. recipe.yaml is the file actually used (deadline-cloud.yaml declares buildTool: rattler-build), so this is the metadata that ends up in the published maya-mtoa package:

• homepage: https://www.autodesk.com/products/maya/overview → the sibling meta.yaml in this same directory correctly points at the Arnold for Maya user guide.
• summary: describes Maya ("professional 3D software for creating realistic characters...") instead of Arnold. meta.yaml has the Arnold summary.
• license: LicenseRef-AutodeskEULA vs. Commercial in meta.yaml — the two recipes for the same package disagree.

Worth syncing about with meta.yaml (or vice versa) so the built package is not advertised as Maya.