wxWidgets upgrade to lower version?

[Jyrki Wahlstedt]

Sorry
to come into this this late, but some background info for this might  
be useful. There would be no trouble at all keeping wxWidgets at the  
latest stable version, but and this is a big but, the upstream  
maintainer of wxPython has the convention of including wxWidgets  
sources in his own releases. Now there would be no trouble, if the  
releases were in sync, but it so happens that with some of wxPython  
releases the included wxWidgets has some features not present in the  
stable version.
With 2.8.9 and 2.8.10 there are these discrepancies, due to which the  
downgrade was necessary.

PS I tried a few times to get the wxPython release system to make more  
sense by having the releases in sync (wouldn't even be necessary to  
include wxWidgets!), but with no success. Sorry for the tone of this  
message, but I am quite bitter about this, problems are thrown upon us  
with no way out.

On 26.6.2009, at 2.31, Ryan Schmidt wrote:

> On Jun 25, 2009, at 17:57, Darren Weber wrote:
>
>> Yea, just read the `port cat wxWidgets` but didn't check any svn  
>> logs.  That may explain the upgrade, but it's curious the version  
>> dropped back because the current stable release is at 2.8.10  
>> according to the downloads:
>> http://www.wxwidgets.org/downloads/
>
> As jameskyle said in the commit message you quoted below, wxWidgets  
> was downgraded back to 2.8.9 for compatibility reasons. I don't have  
> more details than that.
>
>> It's a pity the epoch had to be created, because, as I understand  
>> it, the port will now forever need an epoch number.
>
> I'm not certain why people think that's a pity. Yes, an epoch line  
> will need to remain in wxWidgets forever, but why is that a problem?
>
>> So, out of curiosity, what happens when this port is actually  
>> upgraded to the 2.8.10 release?  Can the epoch remain at 1 and the  
>> version bump up to 2.8.10 - will that trigger an upgrade?  Or does  
>> the version have to bump up for each new release version?
>
> The epoch can stay at 1 until someone wants to do another downgrade.  
> MacPorts basically concatenates the numbers epoch_version_revision,  
> so we had the sequence:
>
> 0_2.8.9_0
> 0_2.8.10_0
> 1_2.8.9_0
>
> If we later update to 2.8.10 again after resolving whatever the  
> issues were, it will be:
>
> 1_2.8.10_0
>
>
>> It helps to have access to the svn logs:
>>
>> [ dweber at X ~/macports/dports/graphics ]$ svn log wxWidgets
>> ------------------------------------------------------------------------
>> r52662 | ryandesign at macports.org | 2009-06-20 14:18:32 -0700 (Sat,  
>> 20 Jun 2009) | 2 lines
>>
>> wxWidgets: increase epoch so everyone who had 2.8.10 installed gets  
>> prompted to downgrade to 2.8.9.
>>
>> ------------------------------------------------------------------------
>> r52414 | jameskyle at macports.org | 2009-06-15 21:34:25 -0700 (Mon,  
>> 15 Jun 2009) | 3 lines
>>
>> Dropped the wxwidgets version to 2.8.9 for compatibility reasons
>> Fixed #19191
>>
>> ------------------------------------------------------------------------
>> r52309 | jameskyle at macports.org | 2009-06-13 16:05:10 -0700 (Sat,  
>> 13 Jun 2009) | 2 lines
>>
>> Disabled parallel builds; fixes #16099
>>
>> ------------------------------------------------------------------------
>> r48246 | mww at macports.org | 2009-03-17 10:41:18 -0700 (Tue, 17 Mar  
>> 2009) | 2 lines
>>
>> version 2.8.10
>>
>> ------------------------------------------------------------------------
>> r40194 | jwa at macports.org | 2008-09-24 08:46:52 -0700 (Wed, 24 Sep  
>> 2008) | 2 lines
>>
>> version bump to 2.8.9
>
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev