Arch Linux is a versatile distribution for experienced users. However, officially, it only supports x86-64 architecture.
Other distributions have been making progress to support various newer architectures, including ARM and RISC-V. Whether it is Ubuntu or an Arch-based distro like Manjaro, you can find official support for ARM/RISC-V.
Unfortunately, that has been missing with Arch Linux, even if there are unofficial ports making good progress.
To change that, Arch Linux has finally decided to set up a test integration for "Arch Linux Ports".
What Does This Mean?
Simply put, unofficial ports for various architectures will get infrastructure and better community-based support until they are integrated in the main Arch Linux repositories.
Arch Linux wants to work on the unofficial ports for other architectures through a joint effort.
To achieve this, a new proposed system was merged as the Arch Linux Ports RFC, which should help Arch Linux help adapt to newer architectures without fully committing to it in its initial phase.
The merged RFC mentions:
This RFC outlines a data driven process through which we can estimate how much extra maintenance effort is required, how mature the architecture is, and how much interest there is for it in the community.
So, as the work/tests progresses for an architecture, it would be easy to evaluate if an architecture can be maintained as an official port or not.
Yes, there is no guarantee that the unofficial ports for ARM/RISC-V will be promoted as official ones, nor there is an estimated time for it. But the system looks promising.
In the past, some RFCs tried to integrate newer architectures directly, but it was not a streamline process (or something that ended up working).
So, with this RFC, Arch Linux has decided to put a system in place that will help them adapt to newer architectures.
The RFC explains the process when a new port starts:
New ports are added by proposing them in an RFC. At least two package maintainers have to lead a port to ensure it will be developed longer term.
Once an introduction RFC is accepted, the work on a port may start. Initial work includes additions of port specific integration (e.g. custom pacman.conf, makepkg.conf, etc.) to the official build tooling.
Port maintainers are expected to work together with relevant Arch Linux teams to enable the setup of any required infrastructure. Required changes to existing tooling should be proposed and if possible also implemented by port maintainers, to ease the workload on the existing teams.
Furthermore, the port maintainers have to be included as package maintainers in the Arch Linux team to be able to access dedicated build infrastructure (and will be expected to maintain/improve it).
Arch Linux + Port Maintainers Work Together
The new RFC encourages the port maintainers and the Arch Linux team to work together towards supporting newer architectures.
Arch Linux says that they have taken inspiration from Debian Ports, which has tried to do something similar.
I believe this is the right direction to go forward, and should help us get official ARM and RISC-V support in the near future. You can take a look at the RFC for more technical details.
💬 What do you think about this RFC? Let me know in the comments down below!
Suggested Read 📖
Dimitrios
Here's why you should opt for It's FOSS Plus Membership
- Even the biggest players in the Linux world don't care about desktop Linux users. We do.
- We don't put content behind paywall. Your support keeps it open for everyone. Think of it like 'pay it forward'.
- Don't like ads? With the Plus membership, you get an ad-free reading experience.
- When millions of AI-generated content is being published daily, you read and learn from real human Linux users.
- It costs just $2 a month, less than the cost of your favorite burger.
