Parch

Component map

Every Parch component, its upstream, and its source. Keep this map honest: it is how contributors figure out where a change belongs.

Parch-maintained components

ComponentRepositoryLanguageRole
Pastor (Parch Store)pastorRustSoftware store and package browser
Parch Welcomeparch-welcomeRust + libadwaitaFirst-run assistant
parch-updateparch-updateShellUpdate notifier/applier with systray applet
Parch Kernel ManagerPKMPython + GTK4/libadwaitaKernel browsing and installation
MirrorManmirrormanRustMirror ranking and switching
GameHubgamehubRustGaming toolkit
Parchdroidparchdroid + parchdroid-kcmPython / C++Android apps via Waydroid
PordlepordleRustPersian word game
Parch Driver ManagerParch-Driver-ManagerPythonVendor driver detection/install
plasma-setupplasma-setupC++Plasma first-run setup
systunersystunerCSystem tuning
parchprobeparchprobeZigHardware probe
archinstall-rsarchinstall-rsRustTUI installer (new generation)
Calamares (Parch)calamares-parchQML/ShellInstaller branding, modules, presets
base-configbase-configShellBase system configuration
parch-configparch-configShellSystem configuration tooling
gnome-parchgnome-parchShellGNOME theming and integration
parch-sddmparch-sddmQMLSDDM login theme
parch-grub-themeparch-grub-themeShellGRUB theme
parch-plymouthparch-plymouthShellBoot splash
parch-persian-fonts / arad-fontspkgbuilds, world-Persian font packaging
ISO profilesparch-iso-*ShellOne repo per edition
world / Voidworld, VoidPython toolingPackage repositories

Consumed from upstream, unmodified

  • Arch Linux repositories core and extra (the bulk of any installed system).
  • The Linux kernel, systemd, mkinitcpio, pacman.
  • KDE Plasma, GNOME, XFCE, Hyprland, and their applications.
  • Calamares upstream (the Parch flavor packages configuration on top).

Parch-modified upstream

UpstreamParch packageWhy
archisoarchiso 99-1 in worldParch build patches and defaults
Calamarescalamares 3.4.3-8 in worldParch modules and fixes

When a Parch-modified package drifts too far from upstream, the maintenance cost shows up at every upstream update. The decision framework (patch downstream, fix upstream, or fork) is in Packaging and Distribution development.

Ownership boundaries

  • Upstream bug: file it upstream; Parch tracks the fix.
  • Parch packaging bug: fix in the PKGBUILD or the component repo.
  • Unclear: ask in the component repo's issue tracker before patching.