[MacPorts] #43749: Macports install: keep repeating in .profile...
#43749: Macports install: keep repeating in .profile... -----------------------+-------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Keywords: | Port: -----------------------+-------------------------------- I just notice: {{{ $ ls -l .profile* -rw-r--r-- 1 myuser staff 1351 17 mai 21:39 .profile -rw-r--r-- 1 myuser staff 241 10 déc 05:57 .profile.macports- saved_2014-03-02_at_22:22:53 -rw-r--r-- 1 myuser staff 611 2 mar 22:22 .profile.macports- saved_2014-03-23_at_12:16:49 -rw-r--r-- 1 myuser staff 981 23 mar 12:16 .profile.macports- saved_2014-05-17_at_21:39:03 }}} and .profile {{{ # MacPorts Installer addition on 2013-12-10_at_11:57:29: adding an appropriate PATH variable for use with MacPorts. export PATH=/opt/local/bin:/opt/local/sbin:$PATH # Finished adapting your PATH environment variable for use with MacPorts. ## # Your previous /Users/my-user/.profile file was backed up as /Users/my- user/.profile.macports-saved_2014-03-02_at_22:22:53 ## # MacPorts Installer addition on 2014-03-02_at_22:22:53: adding an appropriate PATH variable for use with MacPorts. export PATH=/opt/local/bin:/opt/local/sbin:$PATH # Finished adapting your PATH environment variable for use with MacPorts. ## # Your previous /Users/my-user/.profile file was backed up as /Users/my- user/.profile.macports-saved_2014-03-23_at_12:16:49 ## # MacPorts Installer addition on 2014-03-23_at_12:16:49: adding an appropriate PATH variable for use with MacPorts. export PATH=/opt/local/bin:/opt/local/sbin:$PATH # Finished adapting your PATH environment variable for use with MacPorts. ## # Your previous /Users/my-user/.profile file was backed up as /Users/my- user/.profile.macports-saved_2014-05-17_at_21:39:03 ## # MacPorts Installer addition on 2014-05-17_at_21:39:03: adding an appropriate PATH variable for use with MacPorts. export PATH=/opt/local/bin:/opt/local/sbin:$PATH # Finished adapting your PATH environment variable for use with MacPorts. }}} Maybe if an appropriate chained is already present, no need to further write more .profile ... Also it can be in .bash_profile or any user file, so ... or is it the official way to keep base install history ;-) ? -- Ticket URL: <https://trac.macports.org/ticket/43749> MacPorts <http://www.macports.org/> Ports system for OS X
#43749: Macports install: keep repeating in .profile... ------------------------+-------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | ------------------------+-------------------------------- Comment (by ryandesign@…): The code that adds to your shell startup file only runs when you run the package installer downloaded from our web site. You should normally only need to do that once; thereafter you can use "`sudo port selfupdate`", unless your network does not allow rsync traffic. The code that adds to your shell startup file knows about the different shell startup files that are used by bash and tcsh and tries to pick the best one to modify. Also, it does not modify the file if the MacPorts prefix is already in your PATH. So perhaps in your case you have multiple shell startup files, and MacPorts has picked the wrong one, and it's therefore not actually getting into your environment, and therefore MacPorts keeps trying to modify the file again? If you can suggest any improvement to [browser:trunk/base/portmgr/dmg/postflight.in the code that does this], please do. -- Ticket URL: <https://trac.macports.org/ticket/43749#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts