FS#49965 - [makepkg] Build packages in isolation
Attached to Project:
Pacman
Opened by TesX (tesfabpel) - Wednesday, 06 July 2016, 06:30 GMT
Last edited by Allan McRae (Allan) - Friday, 30 December 2016, 02:41 GMT
Opened by TesX (tesfabpel) - Wednesday, 06 July 2016, 06:30 GMT
Last edited by Allan McRae (Allan) - Friday, 30 December 2016, 02:41 GMT
|
Details
Summary and Info:
When trying to install the AUR package `itch` (https://aur.archlinux.org/packages/itch/), the PKGBUILD executes some actions that will affect the system and escape the package manager's control, as reported in comments by some users... Could this be fixed by limiting write access only to the build directory of makepkg? Is there any reason not to? Steps to Reproduce: Try to install some misbehaving package (for example, itch) |
This task depends upon
Closed by Allan McRae (Allan)
Friday, 30 December 2016, 02:41 GMT
Reason for closing: Deferred
Additional comments about closing: devtools is the current solution.
Friday, 30 December 2016, 02:41 GMT
Reason for closing: Deferred
Additional comments about closing: devtools is the current solution.
PKGBUILDs are Bash, they can do stupid things. The one in question does stupid things (npm install)