<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 1 Feb 2017, at 14:20, Bachsau <<a href="mailto:web@bachsau.name" class="">web@bachsau.name</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Am 01.02.2017 um 07:38 schrieb Ryan Schmidt:<br class=""><blockquote type="cite" class="">Sorry. Repeated modifications of the profile when the modifications were already there was a bug. It looks like a fix was committed, so hopefully 2.4.1 will not have this bug anymore.<br class=""></blockquote><br class="">Not only repeated modifications. It simply should not do that in any case, without asking back! </div></div></blockquote><br class=""><div>It is not uncommon to have your profile modified. The <a href="http://python.org" class="">python.org</a> installer will do this.</div><div>But in that case there is a Customise button that allows you to turn this off.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""><blockquote type="cite" class="">Using /etc/paths to add the MacPorts paths is not recommended because that appends the MacPorts paths to the default, while we want the MacPorts paths to be prepended. We want MacPorts versions of software to supersede probably older versions provided by the OS, not vice versa as using /etc/paths will do.<br class=""></blockquote><br class="">It depends on the order in your /etc/paths. If I put it first, it is first. The advantage of /etc/paths is it is applied even to the graphical environment, not just when running a login shell.<br class=""></div></div></blockquote><div><br class=""></div><div>The fix that I contributed fixed the bug and will in fact take into account your edits to /etc/paths as there terminal will start with PATH set to this.</div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div class=""><br class=""><blockquote type="cite" class="">The MacPorts installer has always done this. I'm pretty sure it tells you it will do this, and our documentation says so too.<br class=""></blockquote><br class="">It did not, never.</div></div></blockquote><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class=""><blockquote type="cite" class="">The alternative is that the user installs MacPorts, then when they try to use it they get an error that "port" could not be found in the path; this will cause tons of support requests that I would prefer to avoid, so I'd like to keep things the way they are, with the installer modifying the user's profile when needed.<br class=""></blockquote><br class="">People using MacPorts are those who know about the insides of their system and want to customize it. I think they should at least be able to read and follow documentation.<br class=""><br class=""></div></div></blockquote></div><br class=""><div class="">I don’t think its safe to assume all MacPorts uses are expert admins.</div><div class=""><br class=""></div><div class="">Barry</div><div class=""><br class=""></div></body></html>