On May 15, 2007, at 10:58, James Berry wrote:
On May 14, 2007, at 11:51 PM, Ryan Schmidt wrote:
On May 13, 2007, at 09:54, Randall Wood wrote:
couldn't find HOME environment variable to expand path
while executing
"file mkdir $macports_user_dir"
(procedure "dportinit" line 45)
invoked from within
"dportinit ui_options global_options global_variations"
Error: /opt/local/bin/port: Failed to initialize ports system,
couldn't find HOME environment variable to expand path
Sigh... Now I'm experiencing this error as well, when running port
from a PHP script through my web server:
If I manually create /Library/WebServer/.macports and set it owned
by www, then MacPorts relents. But I'd rather not have to do that.
I think I would prefer that if the HOME environment variable is
not set, that MacPorts not complain about it, and learn to live
without a ~/.macports directory. There's nothing in it anyway, and
my PHP script used to work just fine in previous versions of
MacPorts.
Ryan and Randall,
I checked in some code this morning that should only try to use or
create that directory if HOME is defined. Please check it out and
give feedback. r25177.
Just wanted to confirm with you that yes, this does work. Thanks, James!
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
