Open kingy9000 opened 8 years ago
There is no way this could be done efficiently through bash, but using pacconf
from pacutils might be just what is needed to solve this issue.
Delaying to pacaur 5.0.
Thanks for your quick response.
After thinking on it, I realized it might be more doable to allow /etc/xdg/pacaur/config
or ~/.config/pacaur/config
to be able to source files.
For example the default pacaur config could source /etc/pacman.conf
by default while allowing the user to change it to whatever they want.
To me this sounds like an easier solution to implement but could be wrong.
Thanks for reading.
The current code doesn't allow an easy workaround for your user case. There will be lot of internal changes in the upcoming major version (v.5.0.0), I'll ensure that included files in pacman.conf are correctly taken into account.
Using pacconf will be also useful for removing hardcoded /var/cache/pacman/pkg/ path (see #519).
See also the pacman-dev mailing list.
What is your idea to start working with this? Wrapping pacconf
as makepkg
and cower
is wrapped?
Edit: Obviously this will add pacutils
as new dependency.
I haven't had a close look at this yet. I delayed it to a future version in part because it added a new AUR dependency, but pacutils has been available in the repo for a few months now.
Pacaur fails to properly source files defined in /etc/pacman.conf via "Include=/path/to/file" as explained in this link: Arch Wiki - Pacman - Maintain several configuration files.
For example, when I define:
in a separate file and source it in
/etc/pacman.conf
via the method explained above, I can see colors in pacman but fail to see colors in pacaur when using them. When I write that directly in/etc/pacman.conf
, by uncommenting the Color option that is already there by default, I see colors both in pacman and pacaur when using them.Would highly appreciate if this was fixed, thanks for reading.