[MacPorts] #40347: py26-pyphant: use python PortGroup, merge multiple ports into subports, upgrade to version 1.0b2
MacPorts
noreply at macports.org
Tue Feb 25 11:28:27 PST 2014
#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:15 rowue@…]:
> I think we should focus on future (perhaps simply drop this variant).
I totally support dropping wxpython-2.8. That would simplify the port a
lot. You just need to make sure that you also change `py-sogl` where you
declared a dependency on `wxpython-2.8` (the only reason for that was
`pyphant` that couldn't be built against wxwidgets 3.0 earlier).
If I was you, I would declare dependency on wxpython-3.0 (both in pyphant
and sogl) and stop worrying.
> We also like to do this step by step, so we decided to work along wx-3.0
at first and after everything is fine and settled (including openening
maintainership) move on to the subports.
Subports are straightforward and don't require any larger abount of work
or thinking, you take my example (and modify/ignore my changes for option
names). Once you move, changing the rest will become easier as well.
> As i remember you also had some notices about our app bundle (which we
have cleaned up a little bit by now),
I wanted to clean exactly those bits and pieces that you already fixed.
Earlier you manually copied files to assemble the app, now that happens in
a Portgroup which is a lot cleaner. (Pyphant sources could in principle
also build the app by themselves, but I wouldn't worry about that now. You
can take care of that later.)
(Maybe I was talking about conflicts between Pyphant.app when using Python
2.6 vs. Python 2.7, but if you call the app Pyphant-2.X.app you are on the
safe side, so I wouldn't bother right now either.)
> so I would suggest, we first fix the app bundle and afterwards move to
subports.
The app bundle basically works – apart from the fact that it tries to use
X11 when there's no reason to do so. I would look into optimizing other
issues, in particular it would be nice if there was no need for an
intermediate shell script, to figure out if it's possible to change the
icon etc., but those are minor issues. No hurry about those.
--
Ticket URL: <https://trac.macports.org/ticket/40347#comment:16>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list