wxPython versus wxWidgets

[Mojca Miklavec]

On Wed, Aug 14, 2013 at 3:29 PM, Michael Dickens wrote:
>
>> It's definitely suboptimal, but it's the best that I came up with so
>> far. (To me it's also a bit confusing that wxWidgets-python fetches
>> the sources from wxPython and not from wxWidgets.)
>
> The current wxPython-3.0 could be named, instead,
> wxWidgets-from-wxPython-3.0, which is even more awkward than
> wxWidgets-python, but it is, at least, "truth in advertising" and very
> distinctive.  Not simple (one of your conditions),

I just came to a different idea, reversing yours: wxWidgets-for-wxPython-3.0 ;)

I could make a simple subport of wxWidgets-3.0. All it would do would
be to install wxWidgets 2.9.4 (from wxWidgets, it doesn't need to be
from wxPython as long as the versions are compatible) to the same
location, ${frameworks_dir}/wxWidgets/Versions/wxPython/2.9.

Once wxPython is upgraded to 2.9.5, the subport could install exactly
the same files as the main port, only to a different prefix (wxPython
instead of wxWidgets). If wxPython ever becomes incompatible with
wxWidgets, the port could fetch the files from wxPython again.

What do you think?

> but then the only
> time it will be installed is when installing py-wxpython-3.0

Also in (at least) the following ports:

- gis/grass
- science/gnuradio
- science/stimfit

Mojca