Oops. Hit reply instead of reply all...<br><br>---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">Randall Wood</b> <<a href="mailto:randall.h.wood@alexandriasoftware.com">
randall.h.wood@alexandriasoftware.com</a>><br>Date: Dec 2, 2007 3:41 PM<br>Subject: Re: Added support in MacPorts base to set PATH and MANPATH automatically in Leopard<br>To: Juan Manuel Palacios <<a href="mailto:jmpp@macports.org">
jmpp@macports.org</a>><br><br></span><br><br><div><span class="q"><span class="gmail_quote">On 12/2/07, <b class="gmail_sendername">Juan Manuel Palacios</b> <<a href="mailto:jmpp@macports.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
jmpp@macports.org</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>On Dec 2, 2007, at 2:06 PM, James Berry wrote:<br><br>> Hi Juan,<br>><br>> On Dec 2, 2007, at 9:50 AM, Juan Manuel Palacios wrote:<br>>> So, has any conclusion been reached for this issue? I'm inclined
<br>>> to backing this feature out of the release_1_6 branch until a<br>>> working consensus is reached, and only release it to the public at<br>>> that time (in 1.6.x (x > 0)). Until now we've only been modifying
<br>>> the user "profile" for a range of bourne based shells and the<br>>> "cshrc" file for equivalent C based shells, which has worked fairly<br>>> well, I believe; anyone experienced enough to create something like
<br>>> ~/.bash_profile or anything else very shell specific would be savvy<br>>> enough to setup his/her own environment to their content, I'm sure.<br>>> I'd strongly favor sticking to this approach in
1.6.0 until<br>>> something better is found, unless it explicitly breaks expected<br>>> behavior on Leopard. Does it?<br>><br>> Well, given that man pages are broken at present with a standard<br>> MacPorts install under Leopard, something has to be done. A few
<br>> choices:<br>><br>> (1) Use this scheme, as implemented. (Downsides: affects /etc,<br>> MacPorts paths are added at the end of PATH and MANPATH).<br><br><br> I'm uncomfortable with this approach, as already noted in my previous
<br>mail.</blockquote><div><br> </div></span><div>If Apple provides a mechanism for third-party developers to append paths to PATH and MANPATH without changing any user or system-installed file, then I think we should use it. We may want though (if this would work--I don't know if symlinks would be honored or if only real files would be honored by this mechanism) to use symlinks from /opt/local/etc/[man]path.d/macports to /etc/[man]path.d/macports instead of placing files in /etc/[man]path.d and provide a simple tool (like macports-path-util) to allow users to add/remove those symlinks
</div><span class="q"><br><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">><br>><br>> (2) Supplement this scheme by munging PATH inside the MacPorts code
<br>> to ensure that $prefix is always at the head of the path during
<br>> builds, and to guard against the sort of build problems suggested by<br>> kvv.<br><br><br> MacPorts already sets its internal path for a few things, so this<br>suggestion may be easy to implement but might, just might, have
<br>repercussions that we may want to test more thoroughly (not on the<br>verge of a release, in my opinion ;-)<br><br>><br>><br>> (3) Modify existing path modification code to also add MacPorts<br>> paths to MANPATH. (This might break other man pages on Tiger where
<br>> the system provides no meaningful default for MANPATH—maybe we do it<br>> only if MANPATH is already defined?)<br><br><br> I could definitely look into this extension to the existing<br>postflight script and its implications on both Leopard and Tiger, I
<br>like its "lowest risk" approach. In this case I'll remove the /etc/<br>paths.d and /etc/manpaths.d munging code from the release_1_6 branch<br>to safeguard the release, but will not touch it in trunk so that we
<br>can continue brainstorming over it there.<br><br> Any other suggestions?<br><br> Regards,...<br><br><br>-jmpp<br><br>_______________________________________________<br>macports-dev mailing list<br><a href="mailto:macports-dev@lists.macosforge.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
macports-dev@lists.macosforge.org</a><br><a href="http://lists.macosforge.org/mailman/listinfo/macports-dev" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.macosforge.org/mailman/listinfo/macports-dev
</a><br></blockquote></span></div><span class="sg"><br><br clear="all"><br>-- <br>
Randall Wood<br><a href="mailto:randall.h.wood@alexandriasoftware.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">randall.h.wood@alexandriasoftware.com</a></span><div><span class="e" id="q_1169c97b3a6db465_6">
<br><br>"The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
</span></div><br clear="all"><br>-- <br>Randall Wood<br><a href="mailto:randall.h.wood@alexandriasoftware.com">randall.h.wood@alexandriasoftware.com</a><br><br>"The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."