[MacPorts] #13742: Installation with the package did not run
the postflight script
MacPorts
trac at macosforge.org
Wed Jan 9 14:53:38 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 matrixm at gmail.com):
I just installed macports onto Leopard today. This was a brand new
machine. In fact, it was so new, that the only thing I'd done before
installing macports was to go through the apple pre-install that
configured and set the machine up for the first time, install 10.5.1
update, installed XCode tools off the DVD that came with the machine, then
download and install macports via the dmg image located at
http://svn.macports.org/repository/macports/downloads/MacPorts-1.6.0/MacPorts-1.6.0-10.5-Leopard.dmg
After completeing the install, I found the X11.app and opened it up, and
began to search for ports. The first thing I got was a file not found
error regarding 'port.' So I checked my path, and no /opt directories in
any PATH variable. I discovered that this default user did not have a
.profile, .bash_profile, nor a .bashrc file in the home directory. I'm not
sure if this had any impact on the setting of the PATH/MANPATH variables
or not though.
I grep'd the install log for anythin referring to path, and the only line
that was mentioned during the postflight portion of the log file was that
the MANPATH was already configured correctly for macports, even though it
wasn't.
I did discover that the /etc/paths and /etc/manpaths files existed (which
I hadn't known about until I read through the /etc/profile script). I
added /opt/local/bin and /opt/local/sbin to the /etc/paths file, and then
put /opt/local/man in /etc/manpaths. I'm not sure how the /etc/paths.d and
/etc/manpaths.d files are loaded, but would it be possible to have the
postflight script add the macports directories to either /etc/paths and
/etc/manpaths or do something with a /etc/paths.d/macports and
/etc/manpaths.d/macports file somehow to include those directories?
I'm not sure of the process, but could I be added as a CC for this ticket?
--
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13742#comment:10>
MacPorts </projects/macports>
Ports system for Mac OS
More information about the macports-tickets
mailing list