How to: additional architectures #2660

jaimergp · 2025-11-21T16:03:44Z

PR Checklist:

note any issues closed by this PR with closing keywords
if you are adding a new page under docs/ or community/, you have added it to the sidebar in the corresponding _sidebar.json file
put any other relevant information below

Closes Quansight-Labs/conda-ecosystem-sta-mgmt#58

netlify · 2025-11-21T16:03:50Z

✅ Deploy Preview for conda-forge-previews ready!

Name	Link
🔨 Latest commit	`0a7eb7b`
🔍 Latest deploy log	https://app.netlify.com/projects/conda-forge-previews/deploys/6932bc3b3f3cf70008579e34
😎 Deploy Preview	https://deploy-preview-2660--conda-forge-previews.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 68 Accessibility: 96 Best Practices: 100 SEO: 89 PWA: - View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

mgorny · 2025-11-24T18:20:46Z

docs/how-to/advanced/enable-archs.md

+4. Once a PR is submitted, you can help the feedstock maintainers make the build pass. If you have insight into the particular package, **please** chime in, but most of all **be patient and polite**.
+5. Once the new builds are available from `anaconda.org`, please help the maintainers by testing the packages, and reporting back with any problems… but also successes!


Given that the list says "before submitting a build request", these steps don't seem to fit. I'd either split it into two lists, or perhaps change the heading to indicate the complete process, and add a step "submit the pull request to conda-forge-pinning-feedstock as outlined in the subsequent subsections".

I splitted the last two items in two paragraphs.

mgorny · 2025-11-24T18:22:13Z

docs/how-to/advanced/enable-archs.md

+
+1. Make sure the package is not yet built for that architecture. Consult the package page in anaconda.org: `https://anaconda.org/conda-forge/<package-name>`.
+2. Check if your package is already in the process of being migrated in the [corresponding migration status page](https://conda-forge.org/status/).
+3. Check the feedstock in question to see if there is already an issue or pull request.


I think this needs expanding to answer what to do if there is one. In particular, I think an issue doesn't really change anything per se, but a pull request implies you don't do the steps below.

Added a little sentence (this was carried over from the previous docs)

mgorny · 2025-11-24T18:27:12Z

docs/how-to/advanced/enable-archs.md

+
+## Enable linux-aarch64 and linux-ppc64le
+
+The process is the same as `osx-arm64`. The file to edit is `recipe/migrations/arch_rebuild.txt`, and the status page is [`aarch64andppc64leaddition`](https://conda-forge.org/status/migration/?name=aarch64andppc64leaddition).


Since the steps will always be the same (right?), perhaps it would make sense to move them into the top section, and just list the files, URLs and specific notes in subsections. Maybe even combine everything into a single list, with bullet points for different migrators, and subsections with additional notes. Not sure though, it might actually be more readable this way.

Generally, yes, it has been like that. Let me give it a try.

See 01e6598

mgorny

Overall LGTM, modulo these (I think) typos, and possibly the suggestion.

docs/how-to/advanced/enable-archs.md

Co-authored-by: Michał Górny <[email protected]>

docs/how-to/advanced/enable-archs.md

Co-authored-by: Michał Górny <[email protected]>

mgorny

LGTM.

h-vetinari

I'm completely fine to highly recommend going through the migrators first, but IMO we should demystify the conda-forge.yml configuration for this a bit, which people often seem to get wrong, especially the split between build_platform: and provider: (e.g. some piggyback migrators switch to cross-compilation, and suddenly your build fails; you need to be able to interpret conda-forge.yml to understand what's happening).

I'd describe how to do it manually on the "how-to" page, but I could see the argument to move the "this is how conda-forge.yml works" to another quadrant of diataxis (and if so, I guess we can leave this for another PR).

docs/how-to/advanced/enable-archs.md

Co-authored-by: h-vetinari <[email protected]>

jaimergp · 2025-12-02T09:39:50Z

I think both types of information (how-to, reference) would be useful, but I'll tackle them in separate PRs. Can you approve this one if you agree, @h-vetinari? Thanks!

h-vetinari

I'm fine with this for now, though when we add the reference part, the how-to part should IMO be expanded to contain manual instructions (after xref'ing the reference part).

mfansler · 2025-12-02T13:13:33Z

docs/how-to/advanced/enable-archs.md

+
+- Remove the corresponding line from `conda-forge.yml` and rerender.
+- Add a `skip:` directive to your recipe by matching the non-desired platform, and rerender.
+


Maybe worth adding a complementary note to the one in osx-arm64 about emulation being the current default here, with a link to Emulated Builds section.

Also, somewhere it should be said that cross-compilation is far more efficient (6-7x faster, IME) and that the build_platform can be set to enable this when considering the Arch migration PR. E.g.,

build_platform: linux_aarch64: linux_64 linux_ppc64le: linux_64

With more details in the Cross-Compilation section.

(On a side note, I find it odd the Cross-Compilation section doesn't have an explicit example of the above build_platform config. So maybe it should go there?)

Thanks @mfansler! Check 0a7eb7b and let me know if that suffices!

…nto howto-additional-archs

jaimergp added 4 commits November 21, 2025 16:50

How to: additional architectures

ddc1af6

Update sidebar

49e961e

Link from KB

9b1b891

Add previous steps

7ae35f4

jaimergp requested a review from a team as a code owner November 21, 2025 16:03

This was referenced Nov 21, 2025

How to: keep your fork in sync #2663

Merged

Status Report (2025-11-21) Quansight-Labs/conda-ecosystem-sta-mgmt#98

Closed

mgorny reviewed Nov 24, 2025

View reviewed changes

mgorny mentioned this pull request Nov 28, 2025

Status Report (2025-11-28) Quansight-Labs/conda-ecosystem-sta-mgmt#99

Closed

Reformat guide with general steps

01e6598

mgorny approved these changes Dec 1, 2025

View reviewed changes

docs/how-to/advanced/enable-archs.md Outdated Show resolved Hide resolved

docs/how-to/advanced/enable-archs.md Outdated Show resolved Hide resolved

docs/how-to/advanced/enable-archs.md Outdated Show resolved Hide resolved

jaimergp and others added 2 commits December 1, 2025 15:36

Apply suggestions from code review

c4f7f84

Co-authored-by: Michał Górny <[email protected]>

use anchor links

a912204

mgorny reviewed Dec 1, 2025

View reviewed changes

docs/how-to/advanced/enable-archs.md Outdated Show resolved Hide resolved

docs/how-to/advanced/enable-archs.md Outdated Show resolved Hide resolved

Apply suggestions from code review

9d2b10f

Co-authored-by: Michał Górny <[email protected]>

mgorny approved these changes Dec 1, 2025

View reviewed changes

h-vetinari reviewed Dec 1, 2025

View reviewed changes

docs/how-to/advanced/enable-archs.md Outdated Show resolved Hide resolved

Update docs/how-to/advanced/enable-archs.md

ca09974

Co-authored-by: h-vetinari <[email protected]>

h-vetinari approved these changes Dec 2, 2025

View reviewed changes

mfansler reviewed Dec 2, 2025

View reviewed changes

jaimergp added 2 commits December 5, 2025 11:58

Merge branch 'main' of github.com:conda-forge/conda-forge.github.io i…

7032767

…nto howto-additional-archs

Mention manual migration and cross-compilation details

0a7eb7b

h-vetinari mentioned this pull request Dec 5, 2025

Status Report (2025-12-05) Quansight-Labs/conda-ecosystem-sta-mgmt#101

Open

		4. Once a PR is submitted, you can help the feedstock maintainers make the build pass. If you have insight into the particular package, please chime in, but most of all be patient and polite.
		5. Once the new builds are available from `anaconda.org`, please help the maintainers by testing the packages, and reporting back with any problems… but also successes!


		## Enable linux-aarch64 and linux-ppc64le

		The process is the same as `osx-arm64`. The file to edit is `recipe/migrations/arch_rebuild.txt`, and the status page is [`aarch64andppc64leaddition`](https://conda-forge.org/status/migration/?name=aarch64andppc64leaddition).


		- Remove the corresponding line from `conda-forge.yml` and rerender.
		- Add a `skip:` directive to your recipe by matching the non-desired platform, and rerender.

Uh oh!

How to: additional architectures #2660

Are you sure you want to change the base?

How to: additional architectures #2660

Uh oh!

Conversation

jaimergp commented Nov 21, 2025

Uh oh!

netlify bot commented Nov 21, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for conda-forge-previews ready!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mgorny left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

mgorny left a comment

Choose a reason for hiding this comment

Uh oh!

h-vetinari left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

jaimergp commented Dec 2, 2025

Uh oh!

h-vetinari left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

netlify bot commented Nov 21, 2025 •

edited

Loading