Opened 12 years ago
Closed 10 years ago
#37426 closed defect (worksforme)
shell paths not adapted by the installer
| Reported by: | jule64@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | |
| Keywords: | Cc: | kurthindenburg (Kurt Hindenburg) | |
| Port: |
Description
the "export PATH=/opt/local/bin:/opt/local/sbin:$PATH" line was not appended to my bash and zsh paths after installing Macport for the first time despite the online documentation saying it should: "If needed your shell configuration files will be adapted by the installer to include the necessary settings to run MacPorts and the programs it installs, but you may need to open a new shell for these changes to take effect."
Change History (7)
comment:1 Changed 12 years ago by jmroot (Joshua Root)
| Keywords: | shell path removed |
|---|---|
| Priority: | Not set → Normal |
| Version: | 2.1.2 |
comment:2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Component: | guide → base |
|---|---|
| Owner: | changed from markd@… to macports-tickets@… |
comment:3 Changed 12 years ago by jule64@…
I did install from the .pkg however I cannot find the install.log. Where would that be?
comment:4 Changed 12 years ago by jmroot (Joshua Root)
It's at /var/log/install.log - note that it contains the logs from all installs so only a portion of it will be relevant to the macports install. Also, the log gets turned over after a while, so the relevant bit may be in another file like install.log.0.bz2 if you've done other installs since macports.
comment:6 Changed 10 years ago by kurthindenburg (Kurt Hindenburg)
Please reopen if this still happens with a current release and attach the .log file
comment:7 Changed 10 years ago by kurthindenburg (Kurt Hindenburg)
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Assuming you installed from the .pkg, please attach the install.log. If you installed from source, your config is not changed; "the installer" refers to the .pkg. Note only bash and tcsh are handled by the postflight script, and if you have a reasonably complex set of config files, it's easy to have the changes made by the installer be ineffective due to later overwriting of the variables.