Macports install: keep repeating in .profile...

[jul_bsd@…]

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 ;-) ?

[ryandesign (Ryan Carsten Schmidt)]

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 the code that does this​, please do.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign@…:

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?

I was mistaken; this problem happened to me too when reinstalling MacPorts on one of our buildbot builders (running El Capitan). The part of the script that's supposed to detect if PATH already contains the MacPorts prefix doesn't seem to be working. I haven't checked if this is because of changes in OS X or changes in the script. The part of the script that detects MANPATH and DISPLAY seems to be working fine.

[neverpanic (Clemens Lang)]

r154110 fixes a part of this that will eventually cause the strings to not appear twice. Finding out why our check for the presence of ${PREFIX} in $PATH doesn't work correctly is still open. We should try

SHELL=/usr/bin/dscl . -read "/Users/${USER}" shell | awk -F'/' '{print $NF}'
$SHELL $LOGIN_FLAG -c '/usr/bin/printenv PATH' | grep "${PREFIX}"

on as many machines possible, especially those where we see it end up twice.

[ryandesign (Ryan Carsten Schmidt)]

Duplicate of #34841.