Support for osx-arm64

[volpatto]

Hi all!

I have been working on a project that some of the new team members are using MacOS ARM-based. We use conda devenv there, and I have been struggling to generate lock files with conda devenv --lock for osx-arm64 platform. Actually, I never managed to generate for this platform since it is not expected by conda-devenv in CondaPlatform and related usages.

Is there any way to support osx-arm64? Would you guys think that it would be good to have? MacOS with ARM has been there for some time now. If this feature is desirable, I can try to implement the osx-arm64 support, please lmk.

[prusse-martin]

Hi.

Would you guys think that it would be good to have?

Yes, I guess =)
A contribution adding that would be welcome.

Apparently most recent MacOs versions default do zsh, to properly support that it will also be needed to update the scripts generators but be aware that recently we found that some conda packages do not support all possible shells (at least under linux).

[volpatto]

Hi.

Would you guys think that it would be good to have?

Yes, I guess =) A contribution adding that would be welcome.

Great! I would be happy to contribute.

Apparently most recent MacOs versions default do zsh, to properly support that it will also be needed to update the scripts generators but be aware that recently we found that some conda packages do not support all possible shells (at least under linux).

Oh, that's a good point. TBH, I am not a macOS user, nor familiar with macOS. I have to double-check what the usual shell is for macOS.

In the meantime, I have a draft that is working apparently. I will open a PR soon.

[volpatto]

PR: #234

[prusse-martin]

BTW, one problem someone in my company did stumble on was (he uses fish as shell in linux):

conda-forge/ctng-compiler-activation-feedstock#81 (comment)

[volpatto]

BTW, one problem someone in my company did stumble on was (he uses fish as shell in linux):

conda-forge/ctng-compiler-activation-feedstock#81 (comment)

Ah, I think I saw this before. Looks like there is no supported solution, but there is this workaround. What should we do? Is it still OK to work on #234 despite this limitation? It seems that the default macOS shell is zsh, which happens to be the same one I use (runs fine).

[nicoddemus]

I think we should assume macOS supports bash and go with it. I don't think this should be a blocker.

[prusse-martin]

... Looks like there is no supported solution, but there is this workaround...

I remember my coworker also used some workaround with a script (call bash to active the env and init a new fish shell IIRC).

... Is it still OK to work on #234 despite this limitation?

Same opinion as @nicoddemus =) "go with it".
Not conda-devenv a specific problem, it affects all "conda world".

... It seems that the default macOS shell is zsh...

I did a quick search the other day and apparently it offer "a good" compatibility with scripts written for bash.

[volpatto]

Thanks, @prusse-martin and @nicoddemus! I have time to get back to this now.

[nicoddemus]

@volpatto please note that there's already work going on in #237.

[volpatto]

@volpatto please note that there's already work going on in #237.

Oh, that's right! I didn't pay attention before, ty. Great, it is even more general than my problem, so I will wait #236.

I think we can close this issue and PR #234.

[nicoddemus]

Fixed in #237.