README: mention ALPM/pacman support

Update the Highlights and Understanding components sections to reflect
that pacman (ALPM) is now a supported component repo alongside RPM.

Assisted-by: Pi (Claude Opus 4.6)
This commit is contained in:
Jonathan Lebon 2026-07-23 10:53:19 -04:00
parent e9ea343de3
commit 8df3cb454b

View file

@ -48,8 +48,8 @@ perform this content-based layer splitting.
## Highlights ## Highlights
- **Content agnostic** — Compatible with RPM-based images, but not only. Other - **Content agnostic** — Compatible with RPM and pacman (ALPM) based images.
package ecosystems can be supported, as well as fully custom content. Other package ecosystems can be supported, as well as fully custom content.
- **Container-native** — Best used as a container image, either as part of a - **Container-native** — Best used as a container image, either as part of a
multi-staged build, or standalone. multi-staged build, or standalone.
- **Zero diff** — Apart from modification time, content is never modified. - **Zero diff** — Apart from modification time, content is never modified.
@ -215,9 +215,9 @@ all files from an RPM belong to the same component. Layers are created based on
found components. found components.
A component repo is a source of data from which components can be created. For A component repo is a source of data from which components can be created. For
example, the rpmdb is a component repo (one can imagine similar component repos example, the rpmdb and the ALPM local database are component repos. There is
for other distros). There is also an xattr-based component repo (see the section also an xattr-based component repo (see the section "Customizing the layers"
"Customizing the layers" below). Multiple component repos can be active at once. below). Multiple component repos can be active at once.
### Customizing the layers ### Customizing the layers