Le 11 oct. 08 à 09:08, Ryan Schmidt a écrit : > On Oct 10, 2008, at 12:19, [EMAIL PROTECTED] wrote: > >> Revision: 40682 >> http://trac.macports.org/changeset/40682 >> Author: [EMAIL PROTECTED] >> Date: 2008-10-10 10:19:39 -0700 (Fri, 10 Oct 2008) >> Log Message: >> ----------- >> cln, nestedsums, qmail-spamcontrol, xloops: Errors in platform >> blocks are now executed in a pre-fetch block. >> >> Modified Paths: >> -------------- >> trunk/dports/mail/qmail-spamcontrol/Portfile >> trunk/dports/math/cln/Portfile >> trunk/dports/math/nestedsums/Portfile >> trunk/dports/science/xloops/Portfile >> >> Modified: trunk/dports/mail/qmail-spamcontrol/Portfile >> =================================================================== >> --- trunk/dports/mail/qmail-spamcontrol/Portfile 2008-10-10 >> 16:44:12 UTC (rev 40681) >> +++ trunk/dports/mail/qmail-spamcontrol/Portfile 2008-10-10 >> 17:19:39 UTC (rev 40682) >> @@ -243,7 +243,9 @@ >> } >> >> platform darwin 6 { >> - return -code error "${name} requires Mac OS X 10.3 or newer." >> + pre-fetch { >> + error "${name} requires Mac OS X 10.3 or newer." >> + } >> } > > What is the difference between "error" and "return -code error"? I > keep learning about new ways of returning errors from ports. It's > disconcerting that there are so many ways. :/ >
None. From the manpages, `error string` <=> `return -code error string` _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
