wxGTK and wxPython 2.6 -- please check out

[Michael Schwendt]

On Tue, 29 Nov 2005 07:36:11 -0500, Matthew Miller wrote:

> On Mon, Nov 28, 2005 at 03:49:38PM -0500, Matthew Miller wrote:
> > > > Also -- I want to rename the python package back to wxPython, instead
> > > > of wxPythonGTK2, to follow the normal practice of keeping the package
> > > > name matching the upstream source tarball. Does anyone have an
> > > > argument against that?
> > > Food for thought at https://bugzilla.fedora.us/show_bug.cgi?id=927
> > > comment 6 onwards.  Note that comment 12 mentions upstream _packages_
> > > being (having been?) wxPythonGTK* even though the tarball is wxPython.
> > Yeah, I think upstream came around to sanity after that conversation. :)
> 
> So, anyway, the second question: how does one actually accomplish this in
> the Extras buildsystem? Both the "old" and "new" names exist; I want to
> revert back to the old one....

In case you meant asking how to do this within CVS, the wxPython module
and its FC-4 and FC-3 branches still exist but are empty. You can copy the
package files from the wxPython2 directory except for the Makefile, rename
the spec file, change the %{name} and add/change the relevant "Provides"
and "Obsoletes" including version and release (so your wxPython packages
upgrade the older wxPythonGTK2 packages).