>> >Problem is that one folder is not enough, because you still need >> >access to >> >the "classic" Unix hierarchy (/usr/bin, /bin, /sbin). >> >Perhaps you also want to use two or more prefixes. >> Hm.. but why? I'd use symlinks eg. /usr/bin/wc -> /opt/gentoo/bin/wc, >> what resolves those problems. >
This may be a problem if /usr/bin/wc is already an executable provided by MacOSX > Or what about a Framework? Care to elaborate? > Is it really possible to find any executable without path resolution? > Only ./myapp doesn't require the shell to use the $PATH variable, but > does use the current (absolute) path ($CWD) in order to start the myapp > binary. You still can do an explicit /usr/bin/wc > > Using "#!/usr/bin/env perl" in a script instead of "#!/usr/bin/perl" > allows perl to be in any location in the path environment. > I am not really interested in finding perl, but instead the executable I want to call (/usr/bin/wc in this case) Besides, if I do a "#!/usr/bin/env perl", I may find the MacOSX provided Perl, not the Perl I installed via Gentoo. Somehow defeats the purpose, doesn't it? Regards Dirk -- [email protected] mailing list
