Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ARM Documentation updates #16

Merged
merged 42 commits into from
Mar 4, 2024
Merged

ARM Documentation updates #16

merged 42 commits into from
Mar 4, 2024

Conversation

aliciaaevans
Copy link
Contributor

@aliciaaevans aliciaaevans commented Nov 14, 2023

  • Add linux-aarch64 to all places the supported architectures are mentioned (still waiting for access to Mac M1 on CircleCI)
  • Update CI Inventory page to include CircleCI for ARM
  • Update Build System page to remove/modify outdated information that should mention both CircleCI and Azure
  • Remove references to TravisCI (unless it is still used somewhere?)
  • Instructions for enabling ARM platforms: additional-platforms

source/faqs.rst Outdated Show resolved Hide resolved
source/index.rst Outdated Show resolved Hide resolved
@Yikun
Copy link

Yikun commented Nov 15, 2023

I guess we also need add doc in somewhere to mention how to enbale linux-aarch64 addtional platform [1] for a package?

extra:
  additional-platforms:
    - linux-aarch64

[1] bioconda/bioconda-utils#923

@daler
Copy link
Member

daler commented Nov 19, 2023

I did a full pass through the docs, doing a lot of cleanup and some organization. Some highlights:

  • overhauled the ci-inventory page into a table. Hopefully way easier to see ALL the moving parts now.
  • added a section on platforms, because I was still confused about aarch64, arm64, linux-aarch64, osx-arm64, etc
  • added a new .. datechanged:: directive, so we can start being better about noting when something was added to the docs
  • updated the build-systems page to be more general (it had a lot of details about how bioconda-utils works, which is overkill)
  • added new aarch64 page. Added it under "developer" docs for now, since current the opt-in mechanism is not intended to be widely used
  • updated number of contributors
  • consolidated the 2 faqs into a single one
  • removed the cb3 page (we've been using conda-build 3 for a while now....) but ported over relevant information elsewhere

source/contributor/build-system.rst Outdated Show resolved Hide resolved
source/contributor/build-system.rst Outdated Show resolved Hide resolved

This is being initially approached as an opt-in process as we make sure
all the moving parts are working correctly. A recipe can be flagged for
building on ``linux-aarch64`` by adding the following to the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we intend to push containers for that as well? I would like to see this :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eventually, yes of course!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But not yet? Should we document that? Or should we add an additional key to enable aarch64 containers?
It would be nice to push them if we activate it in the extra section. But I guess that a different discussion.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm actually unclear on the current status of aarch64 containers. I know there was work on getting base images set up, so it could be that aarch64 containers are already handled. I'm still trying to catch up with the recent work though...I'm sure the answer is in there somewhere and once I figure it out I'll clarify this.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, looks like there was some discussion on the core chat (Oct 18) about not immediately uploading aarch64 containers. I think this will be a different discussion. I'll add a note here that containers are currently not built and uploaded.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the core chat public or it is only for the core team ?
I am aware only of https://app.gitter.im/#/room/#bioconda_Lobby:gitter.im but there is no discussion about containers at Oct 18 there.
Thanks!

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd also like to join the discussion about aarch64 support! : )

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, there are many discussions in many places; the one I found re: containers was indeed in a separate core team chat. However we should be better about consolidating information and discussion, ideally on a single github issue.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Yikun @martin-g FYI, some recent PRs on pushing aarch64 images to biocontainers: bioconda/bioconda-recipes#43995, bioconda/bioconda-recipes#44457, bioconda/bioconda-utils#941 . . . largely merged into bioconda/bioconda-recipes#40550.

source/faqs.rst Outdated Show resolved Hide resolved
source/faqs.rst Outdated Show resolved Hide resolved
source/faqs.rst Show resolved Hide resolved
source/faqs.rst Outdated Show resolved Hide resolved
source/faqs.rst Outdated Show resolved Hide resolved
source/faqs.rst Outdated Show resolved Hide resolved
@daler daler marked this pull request as ready for review November 20, 2023 15:01
@daler
Copy link
Member

daler commented Nov 24, 2023

In thinking about @bgruening's aarch64 container question, I realized I couldn't come up with a clear answer along the lines of, "this specific thing needs to change or be updated in order to fully support aarch64 containers" or "it all looks good". So I took a deep dive into all the containers and wrote up my notes in c69024f. Hopefully this will help inform and clarify future discussions.

source/faqs.rst Outdated Show resolved Hide resolved
source/contributor/build-system.rst Outdated Show resolved Hide resolved
source/developer/ci-inventory.rst Outdated Show resolved Hide resolved
source/developer/ci-inventory.rst Outdated Show resolved Hide resolved
source/developer/ci-inventory.rst Outdated Show resolved Hide resolved
source/developer/dockerfile-inventory.rst Outdated Show resolved Hide resolved
source/developer/repo-inventory.rst Outdated Show resolved Hide resolved
source/faqs.rst Outdated Show resolved Hide resolved
source/faqs.rst Outdated Show resolved Hide resolved
be installed as a run dependency without having to explicitly add it as such in
the recipe. This specification is done in the ``zlib`` recipe itself (which is
hosted by conda-forge), so in general bioconda collaborators can just add
``zlib`` as a build dependency.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find this confusing.
https://github.com/bioconda/bioconda-docs/pull/16/files#diff-5a476a141b5805f24f43cab6c3548f1dd1319013abd9035ef91062a6fcd9a35bR441-R442 says that zlib should be in the requirements:host list.
Here the terminology says build dependency which sounds like requirements:build which is only for the compilers, as explained earlier.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree. I think "host dependency" or "host requirement" would be more clear.

Also, I'd like to share my related open PR #18 to clarify how to handle requirements like zlib that use "run exports"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jdblischak agreed, and will get to #18 soon. I think this should be fixed over there. Any suggestions on what a better example would be?

source/faqs.rst Outdated Show resolved Hide resolved
@daler
Copy link
Member

daler commented Mar 4, 2024

@martin-g thanks again for all the reviews!

@daler daler merged commit f7a025b into main Mar 4, 2024
1 check passed
@martin-g
Copy link
Contributor

martin-g commented Mar 5, 2024

@daler Thank you for all your work on Bioconda!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants