Re: [Pythonmac-SIG] Steps needed to get cvs2svn working on Panther or Tiger (solution)

[Ronald Oussoren]

On Sep 18, 2006, at 9:42 PM, Bob Ippolito wrote:

On 9/18/06, Christopher Barker <[EMAIL PROTECTED]> wrote:

Gerben Wierda wrote:

what shell are you using?

hermione-a:~ gerben$ which python
/usr/bin/python





should do. It would mean that I would get a new python when I call
system utitlities that use Python from the command line (because it

taken as not the right thing to do)

bash (default shell). But my env has not been changed by the Universal pkg. PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/ teTeX/bin/i386-apple-darwin-current I also would wonder if that would be something that the Universal .pkg would have to be inserted at the start of my PATH and that is generally

A) system scripts should have the path to Python hard coded:

#!/usr/bin/python

B) The installer is only supposed to alter your login shell PATH, so
anything called by the system won't be effected.

But anyway, Universal pkg did not set up my PATH for my command line shell.

Curious:

Ronald and/or Bob: isn't it supposed to have? I know it did mine:

There's three different login scripts that bash can use.. The 2.4.3
postflight script knows how to patch .profile and .bash_profile... but
if a .bash_login exists and .bash_profile does not exist then it will
create a .profile that is never used. Perhaps that is what happened?

Ronald

Could be. The script that does the patching is installed into / Application/MacPython 2.4, if someone that knows about all of the details of the startup sequence of bash could have a look at that script I'd appreciate it; that way we could have a fully correct script for 2.4.4 and 2.5.1.

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig