[pacman-dev] [PATCH] Use absolute path for pacman and pacman-conf in makepkg

Eli Schwartz eschwartz at archlinux.org
Mon May 11 13:12:18 UTC 2020

On 5/11/20 9:01 AM, wwijsman at live.nl wrote:
> Right now an unpatched pacman almost works for my use case, but there
> still is one issue with building it. Currently ninja will install the
> bash-completion scripts system wide, regardless of which user runs
> ninja install or what the prefix is. Only if bash-completion is not
> available, will the scripts be installed inside the prefix. The code
> which makes this happen is here: 
> https://git.archlinux.org/pacman.git/tree/meson.build#n46
> This is why I submitted the patch which makes bash-completion optional.
> It may need a different solution, though. Would you take a patch which
> adds an option to install the bash-completion scripts inside the
> prefix? I'd prefer not to maintain any private patches if that's
> possible.


It's simple enough to do, I've just been trying to decide whether I
think it is the right solution before proposing it.

Eli Schwartz
Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1601 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/pacman-dev/attachments/20200511/5ec32dc3/attachment.sig>

More information about the pacman-dev mailing list