Skip to content

Adds AltArch (32-bit) SIG proposal doc#738

Open
anantv-arista wants to merge 1 commit intoAlmaLinux:masterfrom
anantv-arista:anantv/alt-arch-sig
Open

Adds AltArch (32-bit) SIG proposal doc#738
anantv-arista wants to merge 1 commit intoAlmaLinux:masterfrom
anantv-arista:anantv/alt-arch-sig

Conversation

@anantv-arista
Copy link

SIG Proposal for 32-bit Alma 10 support (renamed to 'AltArch')

cc @bennyvasquez

Copy link
Member

@bennyvasquez bennyvasquez left a comment

Choose a reason for hiding this comment

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

A few small suggestions to take into account the RPi builds, and adding Meta as one of the sig leads for the RPi builds.

Copy link
Member

@metalefty metalefty left a comment

Choose a reason for hiding this comment

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

Please keep in mind that AltArch SIG is not exclusively for the x86_32 architecture but for all alternative architectures, including RISC-V and ARM SBCs. The suggested change risks giving the impression that the AltArch SIG is being dominated by x86_32.

My understanding is that, in practice, an x86_32 team (or sub-SIG) will be established within the AltArch SIG.


1. **32-bit RPM Repository**: Maintain and publish a 32-bit (i686) RPM repository for AlmaLinux 10
- Selected packages from the main AlmaLinux 10 BaseOS and AppStream repositories
- Selected packages from the epel 10 repository
Copy link
Member

Choose a reason for hiding this comment

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

Is EPEL necessary? We don't build it for AlmaLinux 9 i686

Copy link
Author

Choose a reason for hiding this comment

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

Hi Andrew.

EPEL did not support x86_32 in the EPEL 9 version as well. Due to this, we had to build the i686 versions of the below list of packages ourselves in our infrastructure. It would be helpful if a certain subset of EPEL packages are also built for i686 by Almalinux. Would this be possible?

It would be a very limited list of packages. There could be other customers who want EPEL x86_32 packages as well.

  • catch2
  • libconfuse
  • libsodium
  • openpgm
  • libftdi
  • python-lz4
  • python-pynacl
  • tomlplusplus
  • zeromq
  • blosc
  • libaec
  • python-numexpr
  • hdf5
  • python-tables
  • libimagequant
  • libraqm
  • python-kiwisolver
  • python-pillow
  • hiredis
  • libcli
  • log4cplus
  • py-radix
  • python-bcrypt
  • python-Bottleneck
  • python-regex
  • re2
  • yaml-cpp
  • ctags
  • gflags

@bennyvasquez
Copy link
Member

The board held off on voting for this one, since the PR is no longer stable. We'll review it at our next meeting!

Copy link
Member

@metalefty metalefty left a comment

Choose a reason for hiding this comment

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

Like other SIGs, the file name shouldn't include "SIG". It should be "AltArch.md".

The purpose of this SIG is to maintain support for alternate (non-mainstream) architectures like x86_32 and Raspberry PI.
This SIG will work in close collaboration with the Core SIG to ensure all builds remain synchronized with the AlmaLinux OS 10 releases and maintains compatibility with RHEL ecosystem standards.

## Rationale
Copy link
Member

@metalefty metalefty Feb 18, 2026

Choose a reason for hiding this comment

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

This rationale only applies to x86_32 builds so I don't think it is right place to putting it directly under AltArchSIG. Therefore, I think it would be better to have the following hierarchical logical structure.

However, I think it is written with too much detail overall. As with the documentation of other SIGs, it should be sufficient to include only a high-level overview. Since details such as the x86_32 schedule are described directly under AltArch SIG, it feels x86_32-centric.

@metalefty
Copy link
Member

I don't think it is necessary to include all the work in this document. As with the docs of other SIGs, providing only an overall high-level overview should be sufficient.

Then we can make it more architecture-neutral. I'd rather think detailed information such as x86_32 timeline and resource considerations should be handled in ALESCo RFCs or SIG meeting minutes.

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.

5 participants

Comments