<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Apr 10, 2014 at 10:50 AM, Chris Jones <span dir="ltr"><<a href="mailto:jonesc@hep.phy.cam.ac.uk" target="_blank">jonesc@hep.phy.cam.ac.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 10/04/14 15:48, Помазёнков Виталий wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes, but MacPorts can control this. Instead of specifying "export<br>
PATH=/opt/local/bin:/opt/<u></u>local/sbin:$PATH" in ~/.bash_profile it can<br>
(and should) specify it system-wide in /etc/bashrc - in this way there<br>
will be no problem with programs which is also installed by Apple like<br>
svn - all programs will be the same version (installed by MacPorts).<br>
</blockquote>
<br></div>
I for one, (and I am sure others too) do not want MacPorts editing system files like /etc/bashrc itself. If you want this, by all means do it yourself, but it should remain an action you have to manually have to do, if you want it.<br>
</blockquote><div><br></div><div>Strong agreement; this is part of what I meant by it being Apple's. For one thing, I don't think Apple promises that /etc/bashrc won't be replaced by an OS upgrade. (Also, seriously don't place path settings in .bashrc / bashrc, it belongs in .profile / .bash_profile / /etc/profile and things like rvm / virtualenv / perlbrew etc. will "randomly" lose their settings if you do it in the per-shell file as it overwrites their changes.)</div>
</div><div><br></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div>
<div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div></div>