Pacman could be replaced by another Rust-based option

  • Arch Linux debate replacing Pacman with ALMP.
  • It won't happen in the short term, and both tools could coexist.

ALPM, a possible replacement for Pacman

Something interesting is happening in the Arch Linux community: there's a project underway that could change the future of... pacman package managerThe idea is to develop a new foundation for package management. Written entirely in Rust, a language that stands out for its security and reliability. This project is known as ALPM (Arch Linux Package Management).

For more than a year, the development of ALPM It has received funding, and that's reflected in the progress. Clear specifications have already been defined regarding how the packages should be structured, how to handle the data, and what cryptographic mechanisms to use to guarantee the integrity and authenticity of the system files. It's not just a theoretical idea: there's solid work behind it.

Pacman for ALMP? It's a real possibility

This has led many to wonder if Pacman will eventually be replaced. There are significant differences between the two projects, not only technically, but also legally. Pacman is licensed under the GPL, while ALPM uses more permissive licenses such as Apache 2.0 and MIT, which would facilitate its adoption in other projects or contexts without as many restrictions.

For now, there's no official confirmation that Pacman will be removed. One possibility being considered is a hybrid approach: keeping the Pacman command as we know it, but supporting it internally with a modern implementation written in Rust, similar to what has already been done in other distributions with critical system tools.

For now, we are only seeing the first steps of this proposal. Any changes will not be immediate, even though Arch Linux is famous for its rolling release development model and rapid software deployment. Among the remaining questions is what other distributions using the same base, such as Manjaro and EndeavourOS, will do.