Is this true? Am I overlooking something essential?
And, more to the point, is there a nice clean way I can generate a patch
that takes me from wxGTK 2.8.7 as released to a version of the same which I
can build wxPython against?
Is this true? Am I overlooking something essential?
When we moved to SVN we split the wxPython code out into a separate sub-tree, along with the recent tags and branches specific to wxPython. For releases I now make a combined tree in SVN that contains both wxWidgets and wxPython like it used to be, so people using the tag can get it all at one spot. For example the most recent release is here http://svn.wxwidgets.org/svn/wx/wxPython/tags/wxPy-2.8.7.1/
And, more to the point, is there a nice clean way I can generate a patch
that takes me from wxGTK 2.8.7 as released to a version of the same which I
can build wxPython against?
except the 2nd URI will have the wxPython folder and the first one won't so you'll get a bunch of full diffs for the additional files. But if you check out a copy of both then you can do it locally without too much trouble.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Okay, thank you very much. That's exactly what I'm looking for.
What would really help me (which is to say, in the specific, Fedora) most of
all is if wxWidgets (or, you, I guess) would put together wxGTK source trees
for the x.x.x.x releases you use for wxPython. Then I could just build wxGTK
itself from that. I try to stick to the x.x.x.0 wxPython releases when
possible, but obviously that's not always possible.
The current 2.8.7.1 appears to work fine with wxGTK 2.8.7, although I
haven't tested extensively yet. Guarantying that relationship to always be
the case would be super-ideal from a stability point of view (especially for
Enterprise Linux releases).
···
On Wed, Feb 20, 2008 at 02:30:32PM -0800, Robin Dunn wrote:
Okay, thank you very much. That's exactly what I'm looking for.
What would really help me (which is to say, in the specific, Fedora) most of
all is if wxWidgets (or, you, I guess) would put together wxGTK source trees
for the x.x.x.x releases you use for wxPython. Then I could just build wxGTK
itself from that. I try to stick to the x.x.x.0 wxPython releases when
possible, but obviously that's not always possible.
That is essentially what the wxPython src tarballs are, and the wxPy tags in SVN too. They are combined wxWidgets and wxPython source trees, and that combination is what I use for building binaries on all platforms. Some other distros use them that way too.
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!