Provide Paketo buildpacks for multiple architectures

[loewenstein-sap]

While we are considering to close the RFC because it is anyway already partially implemented and the upstream Cloud Native Buildpacks project provides tools to handle multiple architectures, there is work left with stacks, buildpacks and builders that we would like to track in this issue.

• Make sure Noble based stacks are multi-arch ready and tooling is aligned
  @paketo-buildpacks/stacks-maintainers There is at least this PR from @pacostas to align stack tooling for multi-arch.
  cc @paketo-buildpacks/stacks-contributors
• All buildpacks have to support multiple architectures
  • @paketo-buildpacks/java-maintainers
    I guess this is mostly done, although we might consider cleaning up some cut corners (like using purl query for selecting the arch specific dependency). WDYT?
  • @paketo-buildpacks/nodejs-maintainers
    • ARM support for nodejs buildpacks nodejs#995
  • @paketo-buildpacks/dotnet-core-maintainers
  • @paketo-buildpacks/go-maintainers
  • @paketo-buildpacks/web-servers-maintainers
  • @paketo-buildpacks/python-maintainers
  • @paketo-buildpacks/php-maintainers
  • @paketo-buildpacks/ruby-maintainers
• Make sure Noble based builders are multi-arch ready
  @paketo-buildpacks/builders-maintainers I don't know if there is any specific work that needs to be done.
  cc @paketo-buildpacks/builders-contributors
• What to do about Jammy stacks and builders?
  @paketo-buildpacks/stacks-maintainers & @paketo-buildpacks/builders-maintainers Do we want to increase Jammy multi-arch coverage beyond the Java tiny builder or point users to Noble if they need multi-arch?
  cc @paketo-buildpacks/stacks-contributors & @paketo-buildpacks/builders-contributors & @paketo-buildpacks/steering-committee

[pacostas]

• @paketo-buildpacks/nodejs-maintainers
  This is in progress I believe. @pacostas & @mhdawson should we link detailed and concrete issue/pull requests here?

A relevant issue for multi-arch support is this one from @c0d1ngm0nk3y paketo-buildpacks/nodejs#995 . Correct, we are still work in progress on this one, once we have something concrete, we will open a PR.

[loewenstein-sap]

Thanks @pacosta, added it to the description.

[anthonydahanne]

All buildpacks have to support multiple architectures
@paketo-buildpacks/java-maintainers
I guess this is mostly done, although we might consider cleaning up some cut corners (like using purl query for selecting the arch specific dependency). WDYT?

yes, that's correct, it's all done for Java, and the purl query param to choose the arch is indeed not the target.
@dmikusa , libpak v2 fixes that, right?

[loewenstein-sap]

All buildpacks have to support multiple architectures
@paketo-buildpacks/java-maintainers
I guess this is mostly done, although we might consider cleaning up some cut corners (like using purl query for selecting the arch specific dependency). WDYT?

yes, that's correct, it's all done for Java, and the purl query param to choose the arch is indeed not the target. @dmikusa , libpak v2 fixes that, right?

Ok. Ticked Java off the list.

[dmikusa]

libpak v2 fixes that, right?

libpak v2 will fix that. It hasn't been implemented just yet.