Re: Getting try-ark to work (python: A file or directory in the path name does not exist.)

Daniel Joseph Barnhart Clark writes:

> if you try to call something not in the PATH with
> /usr/bin/env you get an error message exactly like the one

Great; that gets us on the road again.

> I was assuming that the environment I invoked try-ark from
> would be inherited, which doesn't seem to be the case. ...

Hmm... This is kind-of a "Sidai thinking" vs normal Unix, I
guess.  Essentially, we (Sidai types) don't want the way a
system gets built to depend on the vagaries of individual
sysadmins' working environments.  We want the PATHs, umasks,
etc., to be part of a site's ARK "specification".

(Remember, of course, that you don't have to do ARK things
our way.)

> Some things (python for one) are in non-standard
> locations, because I want the current installations to be
> throw-away installs only used to bootstrap ark.

This is a very reasonable approach, and any ideas you have
for making it work better will be welcome.

Part of what's going on here is that different people use
this ARK stuff in different ways.  Joel Shprentz does clean
bootstrap-installs every day before breakfast :-)  I, on the
other hand, do a site that was bootstrapped (by someone
else) in late 2001 and has grown organically since then.
The ARK machinery should be able to satisfy both.

Your change to the docs will go in at the next check-in.
Thanks for that.

Will


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf