The fact that people want to do this (and I can kind of understand the
desire to have a way of saying "Stop! This portfile will HURT YOUR
BRAIN on OS foo/architecture bar/whatever") suggests the need for a
ui_fatal procedure, however. That could then be conditionalized to
do the right thing for interactive use only.
- Jordan
On Jun 21, 2007, at 1:14 PM, Landon Fuller wrote:
On Jun 21, 2007, at 02:45, Ryan Schmidt wrote:
On Jun 21, 2007, at 04:31, Ryan Schmidt wrote:
But could you please not output messages and exit merely in a
platform statement? Please do so only within a stage such as pre-
fetch, e.g.:
platfrom darwin 7 {
pre-fetch {
ui_msg "GiNaC is not supported on Panther (OS X 10.3.x)."
exit 1
}
}
Otherwise, people running port info, portindex, etc. on darwin 7
will be inconvenienced by the exit.
Sorry; I didn't see Chris already made these points.
It really bears re-iterating though. Calling exit(1) in a Portfile
is just bad news, at any stage. Maybe we should remove that
procedure from the Portfile Tcl interpreter ...
-landonf
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
