[MacPorts] #38375: Ports depending on wxWidgets* should either use path-style dependencies or variants instead

[MacPorts]

#38375: Ports depending on wxWidgets* should either use path-style dependencies or
variants instead
-------------------------------------------------+-------------------------
  Reporter:  egall@…                             |      Owner:  macports-
      Type:  defect                              |  tickets@…
  Priority:  Normal                              |     Status:  new
 Component:  ports                               |  Milestone:
Resolution:                                      |    Version:  2.1.3
      Port:  codeblocks FileZilla fityk hugin-   |   Keywords:
  app lisaem py-wxpython rt-volume-rendering     |
  usbprog wxd otrproxy                           |
-------------------------------------------------+-------------------------

Comment (by mojca@…):

 I just checked FileZilla and otrproxy. Neither of them compiles with
 wxWidgets 2.9.

 With FileZilla it's relatively explicit. 4 years ago a ticket (http://trac
 .filezilla-project.org/ticket/4973) has been closed with {{{wontfix}}} and
 the following comment:

 > FileZilla requires wxWidgets 2.8
 >
 > Note that wxWidgets 2.9 is an unstable development version, it shouldn't
 be used in a production environment.

 even though they have a wx3 branch (http://svn.filezilla-
 project.org/filezilla/FileZilla3/branches/), but they haven't touched it
 for three years and I didn't try to compile that one yet.

 Someone submitted a bunch of patches in October 2012 (http://trac
 .filezilla-project.org/ticket/8272). I'm not sure against which version
 exactly, but it's somewhere close to version 3.5.3 and I managed to apply
 the patches. They needed additional fixing (the patches have been tested
 on Windows & Linux, but some additional Mac code needed changes) and still
 didn't compile. They do nightly builds on a Leopard PowerPC machine.

 Anyway: FileZilla requires some effort that goes beyond the scope of
 MacPorts. Someone really needs to collaborate with the upstream developers
 to get it working, otherwise it would be a lot of effort for very little
 benefit.

 The port otrproxy isn't explicit about supporting 2.8 only, but I couldn't
 make it work in a few quick attempts either.

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