Date: Wed, 03 Sep 2003 15:28:48 +0200 From: Bram Moolenaar <Bram@moolenaar.net> To: Thomas Gellekum <Thomas.Gellekum@gmx.de> Cc: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/56365: x11-toolkits/py-wxPython port is broken Message-ID: <200309031328.h83DSmA3078285@moolenaar.net> In-Reply-To: <7vptiiqct5.fsf@edison.en.elsa.intern>
next in thread | previous in thread | raw e-mail | index | archive | help
Thomas Gellekum wrote:
> Bram Moolenaar <Bram@moolenaar.net> writes:
>
> > I don't understand why this patch wasn't already applied, since the
> > wxgtk-2.4.1 port was installed.
>
> I've added that patch only minutes before the py-wxPython upgrade.
Hmm, I did run cvsup this morning (after running into trouble). If you
changed the port yesterday this could explain why I had the non-working
wxgtk installed while the patch was present on my system.
> > I'll attempt doing "make deinstall" and
> > "make install". Since the version number is the same this shouldn't be
> > necessary...
>
> My fault, sorry. I've bumped PORTREVISION in the meantime.
Good. To avoid the problem that I had, can you make the wxPython port
depend on this specific version of wxGTK?
> > But it appears it does help.
>
> Fine.
Certainly. It took me half a day, but now I do have a working wxPython
2.4.1.2.
> > Note that Robin Dunn, the author of wxPython, recommends using the wxGTK
> > included with wxPython instead of a separate one, with the reason that
> > small version differences may cause trouble. Quote:
>
> Well, I don't really want a
> x11-toolkits/wxgtk-for-wxpython-and-dont-mix-with-wxgtk-devel.
No, the files are supposed to be part of the wxPython source archive,
thus you should be able to use them just for wxPython. However, looking
at the unpacked archive I don't see how it works. Perhaps you can ask
details from Robin, it seems he may use a version of wxGTK from CVS in a
next version as well. The problem would come back then.
> > > wxMenuItem::SetMenu was added right after the wxGTK 2.4.1 release was
> > > made. (I thought it was right before, but a quick look at CVS shows
> > > differently. It may be that CVS was tagged earlier than I what I
> > > expected...) Anyway, you'll need to use the wxGTK included in the
> > > wxPythonSrc tarball.
>
> This probably means we'll have to extract the implementation, too.
> I'll take a look at it.
>
> I guess I can close the PR?
Fine with me, I'm happy now. Thanks for your prompt response!
--
LAUNCELOT: At last! A call! A cry of distress ...
(he draws his sword, and turns to CONCORDE)
Concorde! Brave, Concorde ... you shall not have died in vain!
CONCORDE: I'm not quite dead, sir ...
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net \\\
/// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\
\\\ Project leader for A-A-P -- http://www.A-A-P.org ///
\\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html ///
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200309031328.h83DSmA3078285>