On Jun 3, 2009, at 03:06, Scott Haneda wrote:
On Jun 3, 2009, at 12:27 AM, Ryan Schmidt wrote:
On Jun 2, 2009, at 23:54, Scott Haneda wrote:
Does -d suppress 'ui_msg'? I am working on a port, and I am not
getting ui_msg, though I have set one.
It shouldn't be, though it's easy to miss ui_msg output amid the
profusion of debug output.
It is a pretty monstrous ui message, I am not sure I would miss it.
ASSP install to var
$ls -la /opt/local/var/
total 0
drwxr-xr-x 3 root admin 102 Apr 3 01:34 db
drwxr-xr-x 11 root admin 374 Jun 2 19:59 macports
drwxr-xr-x 3 root admin 102 Apr 3 01:34 run
$pwd
/Users/me/macports/mail/ASSP
From the portfile in that above dir:
set assp_base ${prefix}/var/ASSP
if {![file exists ${assp_base}/assp.cfg]} {
...
ui_msg "....... bunch of stuff"
}
$sudo port install
---> Fetching assp
---> Verifying checksum(s) for assp
---> Extracting assp
---> Configuring assp
---> Building assp
---> Staging assp into destroot
---> Installing assp @1.5.1.2_0
---> Activating assp @1.5.1.2_0
---> Cleaning assp
And that my friend, is all she wrote.
Ok, so you're not seeing it even without debug mode.
Here is the entire Portfile
http://dl.getdropbox.com/u/340087/Drops/06.03.09/Portfile-
dea0db16-010530.txt
So your ui_msg is inside an if clause inside the post-activate phase:
set assp_base ${prefix}/var/ASSP
...
post-activate {
...
if {![file exists ${assp_base}/assp.cfg]} {
ui_msg "
....
"
}
}
The only reasons I can see for the message not showing up are 1) the
file ${prefix}/var/ASSP/assp.cfg exists, or 2) you are using direct
mode instead of image mode and therefore there is no activate phase.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
