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#3629 - Updating of $PATH; pacman

Attached to Project: Pacman
Opened by Scott H (stonecrest) - Saturday, 17 December 2005, 05:43 GMT
Last edited by arjan timmerman (blaasvis) - Saturday, 25 March 2006, 22:40 GMT
Task Type Support Request
Category
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

This is the result of a brief forum topic: http://bbs.archlinux.org/viewtopic.php?t=17107

Currently, some apps that install to /opt/* require the user to source /etc/profile or logout/login in order to get their $PATH to update. I see people with this issue over and over, and most find it frustrating. Is there no simple and elegant solution to getting the user's $PATH to update?
This task depends upon

Closed by  Judd Vinet (judd)
Monday, 27 March 2006, 03:51 GMT
Reason for closing:  Won't implement
Comment by Scott H (stonecrest) - Saturday, 17 December 2005, 05:45 GMT
Just to add.. I don't know if this is better suited to pacman or should be done on the PKGBUILD/.install file level. But it would be very helpful for newbies to implement a solution to this.
Comment by Jan de Groot (JGC) - Monday, 19 December 2005, 11:12 GMT
There isn't a solution, since pacman can't update your environment from a (chrooted) subshell.
Comment by Judd Vinet (judd) - Monday, 27 March 2006, 03:50 GMT
Agreed. this would only work for the terminal session that pacman is run in, not the entire environment.

Loading...