Skip to content
This repository has been archived by the owner on May 31, 2018. It is now read-only.

Pacaur fails to properly source files defined in /etc/pacman.conf #433

Open
kingy9000 opened this issue Feb 24, 2016 · 7 comments
Open

Pacaur fails to properly source files defined in /etc/pacman.conf #433

kingy9000 opened this issue Feb 24, 2016 · 7 comments

Comments

@kingy9000
Copy link

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:

[options]
Color

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.

@rmarquis rmarquis added the todo label Feb 24, 2016
@rmarquis rmarquis added this to the 5.x - new features milestone Feb 24, 2016
@rmarquis
Copy link
Owner

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.

@kingy9000
Copy link
Author

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.

@rmarquis
Copy link
Owner

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.

@rmarquis rmarquis modified the milestones: 4.6.x - new features, 5.0.x - later Mar 24, 2016
@rmarquis rmarquis modified the milestones: 4.7.x - new features, 5.0.x - later Oct 1, 2016
@rmarquis
Copy link
Owner

Using pacconf will be also useful for removing hardcoded /var/cache/pacman/pkg/ path (see #519).

@rmarquis
Copy link
Owner

rmarquis commented Jan 21, 2017

See also the pacman-dev mailing list.

@ismaelgv
Copy link
Contributor

ismaelgv commented Apr 24, 2017

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.

@rmarquis
Copy link
Owner

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants