[101250] users/g5pw/dports/python

[Ryan Schmidt]

On Jan 7, 2013, at 04:47, g5pw at macports.org wrote:

> Revision: 101250
>          https://trac.macports.org/changeset/101250
> Author:   g5pw at macports.org
> Date:     2013-01-07 02:47:53 -0800 (Mon, 07 Jan 2013)
> Log Message:
> -----------
> python/py-pyobjc{,-core}:
>  rename py-pyobjc to py-pyobjc-core, unify both ports
>  update to 2.4


> --- users/g5pw/dports/python/py-pyobjc/Portfile	2013-01-07 07:06:23 UTC (rev 101249)
> +++ users/g5pw/dports/python/py-pyobjc/Portfile	2013-01-07 10:47:53 UTC (rev 101250)
> @@ -2,16 +2,19 @@
> # $Id$
> 
> PortSystem 1.0
> -PortGroup python24 1.0
> +PortGroup python 1.0
> 
> name                py-pyobjc
> +replaced_by         py-pyobjc-core
> version             1.4
> +revision            1
> +python.versions     25 26 27 32

You will need to manually and individually handle replacement of each of the old ports. For an example see the py-scikits-umfpack port. There's probably no need to include the python portgroup (or any portgroup other than the "obsolete" portgroup if desired) in replaced ports.


> --- users/g5pw/dports/python/py-pyobjc-core/Portfile	                        (rev 0)
> +++ users/g5pw/dports/python/py-pyobjc-core/Portfile	2013-01-07 10:47:53 UTC (rev 101250)
> @@ -0,0 +1,50 @@
> +# -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- vim:fenc=utf-8:ft=portfile:et:sw=4:ts=4:sts=4
> +# $Id$
> +
> +PortSystem 1.0
> +PortGroup python 1.0
> +
> +set my_name         pyobjc-core
> +name                py-${my_name}
> +version             2.4
> +python.versions     26 27 32 33

So there is no upgrade path for py-pyobjc (the current python 2.4 port) or py25-pyobjc?