[FEATURE] Option to exclude AUR packages from system updates
Los mantenedores suelen responder en 1 día
@mylinuxforwork ya está trabajando en esto.
Desde el 30/8/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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
- Lenguaje dominante
- QML
- Estrellas
- 5.1k
- Forks
- 386
- Merge medio
- 16 h 45 min
- PR fusionados (30 d)
- 14
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de mylinuxforwork/dotfiles
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
mylinuxforwork/dotfiles#1904 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 82/100
mylinuxforwork/dotfiles#1829 ·
Los mantenedores suelen responder en 1 día
-
enhancement solved
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
mylinuxforwork/dotfiles#1807 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
mylinuxforwork/dotfiles#1765 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[FEATURE] add keycap 1 app window over all windowsPosiblemente ocupada @mylinuxforwork la tomó hace 1 día. Abiertoenhancement
mylinuxforwork/dotfiles#1902 · 1 asignado ·
Los mantenedores suelen responder en 1 día