Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#36195 - makepkg does not execute itself in a clean environnement

Attached to Project: Pacman
Opened by Enjolras (enjolras) - Thursday, 18 July 2013, 17:26 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 04 September 2013, 01:18 GMT
Task Type Bug Report
Category makepkg
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 4.1.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

makepkg shell executes pkgbuild using the environnement of the calling shell.

This means that export variables are inherited. For instance, the ocaml package manager changes the library path and the root path for ocaml libraries and binaries.
When opam is installed, building AUR ocaml packages like ocaml-ocamlgraph will write in $HOME/.opam instead of in $pkgdir.
Maybe the PKGBUILD should be written differently, but having a clean environnment sounds like a good idea anyway.
This task depends upon

Closed by  Dave Reisner (falconindy)
Wednesday, 04 September 2013, 01:18 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Use devtools if you need a clean environment.
Comment by Dave Reisner (falconindy) - Thursday, 18 July 2013, 17:33 GMT
If you want a clean build environment, there's a lot more you need to do than just cleanse the process environment. There's a reason that dev-tools exists, and why official packages are built there.

Defining a variable whitelist is going to be just riddled with pitfalls as building in a dirty environment.

Loading...