Hello Alex, you need to create a missing file or give the full path to the port executable. The latter solution means that you have to enter the following on the command line: sudo /opt/local/bin/port -d selfupdate The better solution is to create a file called '.profile' in your home directory. In this file you specify additional directories that are to be scanned for executables and manual entries. The MacPorts installation fails to create this file, so you have to create it manually. To do so copy the following text… export PATH=/opt/local/bin:/opt/local/sbin:$PATH export MANPATH=/opt/local/share/man:$MANPATH …then enter the following command into a new terminal window: pico ~/.profile Paste the text into the terminal window. Press ctrl-x to exit pico, press the 'y' key to confirm that you want to save and press the return key to confirm that the filename should be .profile. The last thing to do is to close the terminal window and open up a new one. Now you will have access to the port executable just by typing 'port'. Best regards, Adrian On Mar 11, 2008, at 5:14 PM, Alex Zavatone wrote:

Hi all. I can't get past line 1 of the initial install instructions after installing the 1.6.0 MacPorts DMG.

Platform: Quad G5, 2G Ram, OS 10.5.2, Xcode 3.1, X11 2.1.1

When I enter the following into the terminal...

sudo port -d selfupdate

I get the following error message: sudo: port: command not found

port is in the root:opt:local:bin directory

Is there some variable in some file that the installer missed?

Also, some of the docs say to use -d, others say -v. A little inconsistency there.

Thanks in advance, - Alex Zavatone _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

On Mar 11, 2008, at 14:42, Alex Zavatone wrote:

On Mar 11, 2008, at 1:23 PM, Adrian Nier wrote:

...

you need to create a missing file or give the full path to the port executable. The latter solution means that you have to enter the following on the command line:

sudo /opt/local/bin/port -d selfupdate

Ok, I rebooted and that worked. Cool.

...

The better solution is to create a file called '.profile' in your home directory. In this file you specify additional directories that are to be scanned for executables and manual entries. The MacPorts installation fails to create this file, so you have to create it manually.

Awesome. Works like a charm on my other mac. Why doesn't the .DMG installer do this?

No "non compiler friendly" user is going to be able to get up and running without this information.

There is a bug in the 1.6.0 dmg installer with the creation of the .profile file, which has already been fixed in trunk, but we have not yet released the new version. I believe our release manager is a bit busy with other tasks and hasn't had the time to make a new release.