[MacPorts] #13742: Installation with the package did not run
the postflight script
MacPorts
trac at macosforge.org
Thu Jan 24 19:44:42 PST 2008
#13742: Installation with the package did not run the postflight script
-------------------------------------+--------------------------------------
Reporter: mellonjasper at gmail.com | Owner: jmpp at macports.org
Type: defect | Status: new
Priority: Normal | Milestone: MacPorts base bugs
Component: base | Version: 1.6.0
Resolution: | Keywords: installation postflight
-------------------------------------+--------------------------------------
Comment (by rui at marinheiro.org):
I'm having the exact same problem. No .profile shows up after installing
Macports on Leopard, using MacPorts-1.6.0.pkg.
Before reading this Ticket, I have tried to reinstall Macport again, and
no luck.
Replying directly to your request:
> Anyhow, can you still tell me the output of the `basename $SHELL`
command?
I also obtained the expected:[[BR]]
{{{
bash
}}}
In the /var/log/installer.log I could find the following output:[[BR]]
{{{
Jan 25 02:24:48 Maresia Installer[148]: Finishing receipt
Jan 25 02:24:48 Maresia Installer[148]: run postflight script for
MacPorts-1.6.0
Jan 25 02:24:48 Maresia Installer[148]: Localized installer script
postflight found in the MacPorts-1.6.0 package. Using compatibility mode.
Jan 25 02:24:49 Maresia runner[152]: postflight[160]: Unknown shell!
Please set your MacPorts compatible environment manually.
Jan 25 02:24:49 Maresia runner[152]: postflight[160]:
Jan 25 02:24:49: --- last message repeated 1 time ---
}}}
I don't know if this output is expected, but for some reason the script
can't determine which shell is being used.
Is there any thing else I can do to fix this problem?
Rui
--
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13742#comment:13>
MacPorts </projects/macports>
Ports system for Mac OS
More information about the macports-tickets
mailing list