When using quickpkg with no options, this will install files with the following header files on the client machine :
# empty file because --include-config=n when `quickpkg` was used
This breaks a lot of packages including:
- dbus (uses XML files, the # tkoen is invalid)
- gdm, does not start because the /etc/dbus-1/system.d/gdm.conf is invalid
- pulseaudio, because /etc/pulse/* are invalid or empty
I think quickpkg --include-config=n should install vanilla configuration files, just like you have installed it by upstream sources.
this isn't possible: quickpkg is creating binpkgs from your installed set of files, and copies are not retained of vanilla config files, nor do we want that.
Okay, but will this also happen if FEATURES=buildpkg is used when building packages?