[MacPorts] #21372: qscintilla port fails to handle python25 dependency (snow leopard)
MacPorts
noreply at macports.org
Tue Mar 16 07:59:09 PDT 2010
#21372: qscintilla port fails to handle python25 dependency (snow leopard)
-----------------------------------------+----------------------------------
Reporter: thomas.mccullough@… | Owner: adfernandes@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port: qscintilla
-----------------------------------------+----------------------------------
Comment(by adfernandes@…):
Okay - I've almost got it, except for what is either (a) a MacPorts bug or
(b) me doing something stupid. Help would be appreciated. :-)
The good news: the `qscintilla` port now builds and installs cleanly,
further installing the `QtDesigner` component. '''However''', I've moved
the python component out to a separate port. Why? I'm creating a port for
the `eric4` python editor. This editor requires the python qscintilla
bindings. If I build python bindings as a variant of qscintilla, there is
no way for `eric4` to ensure that it has the bindings, since dependencies
don't enforce variants.
The weird part is in the new, attached `py26-qscintilla` port that I've
attached. For some reason, it absolutely and completely insists that it
depends on `python25`... but '''only''' when configuring or building. I
can't figure it out... `port -dv extract` and `port -dv patch` both work
just fine. But if I use `port -dv configure` it '''then''' somehow decides
that `python25` is a required dependency. Building, destrooting, and
installing with `port -dvn configure/build/destroot/install` work just
fine.
Is the port written in a weird way that I'm screwing up?
Also - testing would be appreciated before I commit. Thanks, all!
--
Ticket URL: <http://trac.macports.org/ticket/21372#comment:7>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list