Requested Conda osx-arm64 recipe

[cmastalli]

Hi guys,

It would be nice to have the osx-arm64 recipe for Mac M1 users.
Do you think it is possible to deploy it quickly?

If not, could you provide brief instructions how to compile from source the code?
For instance, how should I install omniORB4 and openscenegraph?

Many thanks,
Carlos

[cmastalli]

I know this might be not a priority (amount a list of things to be done).
But, this is blocking me. Is there any possibility to have this recipe?

[traversaro]

@cmastalli fyi to add a conda-forge package to the macOS arm migration you can just open a PR such as conda-forge/conda-forge-pinning-feedstock#2887 . The conda-forge system will add the package (and all its dependencies) to the migration that you can track in https://conda-forge.org/status/#armosxaddition .

[traversaro]

@cmastalli fyi to add a conda-forge package to the macOS arm migration you can just open a PR such as conda-forge/conda-forge-pinning-feedstock#2887 . The conda-forge system will add the package (and all its dependencies) to the migration that you can track in https://conda-forge.org/status/#armosxaddition .

The PR is merged, and now gepetto-viewer-corba is part of the migration, see for example from https://raw.githubusercontent.com/regro/cf-graph-countyfair/master/status/armosxaddition.svg?sanitize=true :

[cmastalli]

The PR is merged, and now gepetto-viewer-corba is part of the migration, see for example from https://raw.githubusercontent.com/regro/cf-graph-countyfair/master/status/armosxaddition.svg?sanitize=true :

Thank you for the instructive comments. May I ask you some other questions?

1. How can we request to include a new package in conda-forget? (does someone create the GitHub repository with all recipes? or do we need to do it ourselves?)
2. What happens if there is a package dependency or error that doesn't allow us to deploy a specific recipe?
3. How long it takes (in average) to have the migration done?

[traversaro]

How can we request to include a new package in conda-forget? (does someone create the GitHub repository with all recipes? or do we need to do it ourselves?)

In a nutshell, you need to provide a PR to https://github.com/conda-forge/staged-recipes, for example conda-forge/staged-recipes#17935 . Detailed instructions: https://conda-forge.org/docs/maintainer/adding_pkgs.html .

What happens if there is a package dependency or error that doesn't allow us to deploy a specific recipe?

Every change in a package is a PR (version bump, update in pinned dependencies, "re-render" of the recipe ). If this change result in a CI failure, the PR does not get merged until somebody fixes it. If your recipe is affected by a some other recipe PR not being merged, either you fix the PR in the other recipe, or you find a local workaround in your recipe.

How long it takes (in average) to have the migration done?

It depends. If all the recipes are building correctly and the migration PR is quickly merged, probably a few days. Otherwise, it depends on how much time does it take for however is interested in fixing the migration PR and make sure that the CI is green.

[traversaro]

An update on this. Fortunatly the migration from qt 5.12 (not available on osx-arm64) to qt/qt-main 5.15 started. For what regards that migration (as described in https://conda-forge.org/status/#qt515 and https://raw.githubusercontent.com/regro/cf-graph-countyfair/master/status/qt515.svg?sanitize=true ) the situation is the following:

So conda-forge/openscenegraph-osgqt-feedstock#5 should unblock it.

[olivier-stasse]

Thanks @traversaro for the update !