... and there's no ebuild for the current stable version (2.2.9). The 2.3.2 ebuild works fine for 2.2.9 however (at least for me). I needed wxGTK-2.2.9 for Audacity (audacity.sourceforge.net), a very nice sound editing tool, it won't compile with 2.3.2.
Okies, I'm going to try this one out and then include in portage, I'm not sure wether to keep the old one or mask it, thats a later issue when/if it works ;)
Hi! I don't remember exactly why I added the development version instead of the stable one, but I'm sure I had a good reason at the time :) Must have been needed as a dependency for another app or something. However, as it appears there is interest in other apps now, I would suggest adding the latest stable version and leave the development version in the tree but package mask it.
Ah! I remember my good reason. Please see http://www.wxpython.org/BUILD.unix.txt wxPython was my original reason for add wxGTK The reason for adding the development version (from the build instruction cited above): ****snip***** B. You'll usually want to use a version of wxGTK that has the same version number as the wxPython sources you are using. (Another advantage of using CVS is that you'll get both at the same time.) *****unsnip**** In light of this, I would add the stable version of wxGTK to the tree while retaining the development version and *not* masking the development version or all things wxPython will presumably break.
okies, its in portage now
