[MacPorts] #40347: py26-pyphant: use python PortGroup, merge multiple ports into subports, upgrade to version 1.0b2

[MacPorts]

#40347: py26-pyphant: use python PortGroup, merge multiple ports into subports,
upgrade to version 1.0b2
---------------------------+----------------------
  Reporter:  mojca@…       |      Owner:  rowue@…
      Type:  update        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:
Resolution:                |   Keywords:  haspatch
      Port:  py26-pyphant  |
---------------------------+----------------------

Comment (by mojca@…):

 Replying to [comment:11 alexander.held@…]:
 >
 > I think we tried setting `worksrcdir` but then also all the git commands
 where executed inside the workdir.
 > We did not investigate this further however.

 When using the GitHub PortGroup there is no git involved at all. I can try
 myself if you don't manage to make it work.

 > If I understood you correctly, the only way to keep `py26-pyphant` would
 be to link both `py26-sogl` and `py26-pyphant` against `py26-wxpython-2.8`
 and to link `py27-sogl` and `py27-pyphant` against `py27-wxpython-3.0`.

 First of all: I wanted to say that linking `py26-sogl` against
 `py26-wxpython-3.0` would be "impossible"/problematic now, when pyphant is
 not yet compatible with wxPython 3.0. That wouldn't work at all.

 Once pyphant starts working with wxPython 3.0, there's no problem if `py-
 sogl` depends on `py26-wxpython-3.0` in principle, but if the user has any
 given port installed that depends on wxPython 2.8, that will generate
 conflicts (and will generate nothing but confusion). In particular
 upgrading `py26-pyphant` will fail and users would need to manually force-
 remove some packages.


 To avoid the conflict:
   * One way is to provide port variants to depend on either wxPython 2.8
 or 3.0. But that's just overcomplicating for no real benefit unless
 wxPython 3.0 support is buggy.
   * Do what you did now: depend on wxPython 2.8 for Python 2.6 and on
 wxPython 3.0 for Python 2.7 also for pyphant, but that's suboptimal and
 ugly. Who would want to use X11 when Cocoa is available? (Other than maybe
 for testing something.)
   * Simply drop support for Python 2.6 and automatically replace
 `py26-pyphant` with `py27-pyphant` when the user tries to upgrade.

-- 
Ticket URL: <https://trac.macports.org/ticket/40347#comment:12>
MacPorts <http://www.macports.org/>
Ports system for OS X