Actionless Loveless

@dhouck so far it can be done only manually in two steps (the ticket is about combining those two steps into one, and defining the list of packages for which...

yeah, you can do it, inside PKGBUILD, next you can do a local commit, and next it will merge it locally during the pulling the newest changes if upstream package...

what about adding an option "Disable systemd dynamic users"?

@sakshatshinde `pikaur/config.py` and `pikaur/main.py`

i am not sure about this, mb to write a warning what it's a group package? because such behavior as you requested could be achieved by: `pikaur -G $(pikaur -Sgq...

btw i've implemented it like that in pikaur because if you do `pacman -Si gnome` it will behave in a similar way

> pikaur is more talkative and misleading. the docu says PKGBUILDs. multiple. it says "reading the package databases" > ` pikaur {-G --getpkgbuild} [options] ` that means what you could...

if pikaur -G will be accepting only one package, it would require writing a shell-iteration to implement this: `pikaur -G $(pikaur -Sgq gnome)` on a user-side and `pacman -Si` also...

> "warning: following packages cannot be found in AUR" "gnome". and this is something what i can actually fix :-)

please attach the full log with --pikaur-debug flag as advised in issue template