[FEATURE] Option to exclude AUR packages from system updates

Aperta
#1,808 3 commenti 1 reazione 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@mylinuxforwork ci sta già lavorando.

Dal 30/8/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement
Is your feature request related to a problem? Please describe.

On existing ML4W installations where an AUR helper such as yay or paru is still installed, the ML4W system updater also includes AUR packages when performing system updates.

I prefer to update official Arch/CachyOS repository packages first and handle AUR packages separately, so I can review PKGBUILD changes before installing them.

I understand that new ML4W OS installations no longer install AUR packages or AUR helpers by default, so this mainly concerns existing/upgraded installations.

Describe the solution you'd like

It would be useful to have an optional setting in ML4W to exclude AUR packages from the system update process.

For example:
Include AUR packages in system updates: On / Off

When disabled:
The update indicator could still show all available updates (official repositories + AUR).
The ML4W system updater would install only official repository packages.
AUR packages would be left for the user to update manually with yay or paru.

The current behavior could remain the default, so this would simply provide an alternative workflow for users who prefer to manage AUR updates separately.

Describe alternatives you've considered

A local modification of ml4w-install-system-updates would be possible, but this would need to be maintained or reapplied after ML4W updates. An official setting would therefore be a cleaner solution.

Additional context

This feature request follows a mail to Stephan, who suggested opening a GitHub issue so the implementation status can be tracked here.

Support or Contribution
Lingua principale
QML
Stelle
5.1k
Fork
386
Merge medio
16h 45m
PR unite (30g)
14

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di mylinuxforwork/dotfiles

Tutte le issue di mylinuxforwork/dotfiles

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.