On Fri, Dec 28, 2012 at 4:31 AM, Ryan Schmidt <[email protected]> wrote: > > On Dec 26, 2012, at 14:23, [email protected] wrote: > >> Revision: 100811 >> https://trac.macports.org/changeset/100811 >> Author: [email protected] >> Date: 2012-12-26 12:23:03 -0800 (Wed, 26 Dec 2012) >> Log Message: >> ----------- >> This time, commit in the right directories. Cf. r100800 >> >> Revision Links: >> -------------- >> https://trac.macports.org/changeset/100800 >> >> Added Paths: >> ----------- >> trunk/dports/python/py32-pyobjc/ >> trunk/dports/python/py32-pyobjc/Portfile >> trunk/dports/python/py32-pyobjc-cocoa/ >> trunk/dports/python/py32-pyobjc-cocoa/Portfile >> >> Added: trunk/dports/python/py32-pyobjc/Portfile >> =================================================================== >> --- trunk/dports/python/py32-pyobjc/Portfile (rev 0) >> +++ trunk/dports/python/py32-pyobjc/Portfile 2012-12-26 20:23:03 UTC (rev >> 100811) >> @@ -0,0 +1,59 @@ >> +# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; >> c-basic-offset: 4 -*- vim:fenc=utf-8:ft=tcl:et:sw=4:ts=4:sts=4 >> +# $Id: Portfile 100801 2012-12-26 13:26:42Z [email protected] $ >> + >> +PortSystem 1.0 >> +PortGroup python32 1.0 >> + >> +name py32-pyobjc > > We shouldn't be adding new ports using the old pythonXX portgroups; we should > be moving existing ports to the unified python port group.
FYI, I've already done all the work for this (and the other py-pyobjc-*) in this ticket: https://trac.macports.org/ticket/37222 Just saying. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
