| 4 | | |
| 5 | | == .profile not set up == |
| 6 | | |
| 7 | | After a fresh installation of MacPorts 1.6.0, the `.profile` is not set up as it should be, with the consequence that the shell says the `port` command is not found when you try to use it. This is [ticket:13742 a bug in the 1.6.0 installer]. It is fixed in MacPorts 1.7.0. |
| 8 | | |
| 9 | | The recommended fix is to install the MacPorts 1.7 .pkg. You could also work around the problem by downloading the corrected `postflight` script and running it manually, like this: |
| 10 | | |
| 11 | | {{{ |
| 12 | | curl -O http://svn.macports.org/repository/macports/branches/release_1_6/base/portmgr/dmg/postflight && bash postflight |
| 13 | | }}} |
| 14 | | |
| 15 | | This will set up your `.profile` for you. After the `.profile` is set up, the script will attempt to run `sudo port selfupdate` but will fail. This is normal in this case. Please ignore the permission errors the `rsync` process will print. When the script finishes, you should run `sudo port selfupdate` manually. |
| 16 | | |
| 17 | | To get the terminal to notice the new `.profile`, close your terminal window and open a new one. |
| 18 | | |
| 19 | | Instead of downloading and running the `postflight` script from the repository, you could alternatively set up your `.profile` manually, as [http://guide.macports.org/#installing.shell explained in the Guide]. |
