[61345] trunk/dports/devel/soprano/Portfile

[Ryan Schmidt]

On Dec 10, 2009, at 07:29, Ryan Stonecipher-Fisher wrote:

> On Wed, Dec 9, 2009 at 6:09 PM, Ryan Schmidt wrote:
>> 
> 
>> On Dec 9, 2009, at 07:38, rmsfisher at macports.org wrote:
>> 
>>> Revision: 61345
>>>          http://trac.macports.org/changeset/61345
>>> Author:   rmsfisher at macports.org
>>> Date:     2009-12-09 05:37:57 -0800 (Wed, 09 Dec 2009)
>>> Log Message:
>>> -----------
>>> devel/soprano upgraded version
>>> 
>>> Modified Paths:
>>> --------------
>>>    trunk/dports/devel/soprano/Portfile
>>> 
>>> Modified: trunk/dports/devel/soprano/Portfile
>>> ===================================================================
>>> --- trunk/dports/devel/soprano/Portfile       2009-12-09 05:54:16 UTC (rev 61344)
>>> +++ trunk/dports/devel/soprano/Portfile       2009-12-09 13:37:57 UTC (rev 61345)
>>> @@ -4,7 +4,7 @@
>>> PortGroup           kde4    1.0
>>> 
>>> name                soprano
>>> -version             2.3.1
>>> +version             2.3.70
>> 
>> Are you sure you want to do that? 2.3.70 is a beta version of 2.4; 2.3.1 was a stable version. As such, 2.3.70 would be more at home in a soprano-devel port.
>> 
>> http://soprano.sourceforge.net/node/40
> 
> It seems to run fine but if you wish to revert to 2.3.1 that may be
> better in case some behavioral quirk is present that I have not yet
> bumped into.

I don't doubt it appears to run fine for you, but your testing was probably not exhaustive, and there may be cases where this pre-release version doesn't work perfectly; if it did, I have to assume the developers would have released it as a stable version. In MacPorts we like to offer stable versions, not development versions (except in -devel ports); see the ongoing discussion on this list about -devel ports and wxWidgets. Unless there is a reason why 2.3.1 totally doesn't work anymore, the port should be downgraded back to 2.3.1. To do that, you'll have to increase the port's epoch from its default 0 to a higher integer, for example 1, so that anyone who already upgraded to 2.3.70 will be prompted to downgrade again.

> Is there an easy way to determine that a livecheck suggestion is not a
> stable release?


No, you just have to know the versioning scheme used by the software. Some projects use the "2nd digit is odd" rule for unstable releases (cairo, glib2, graphviz, libpixman, pango, wine). Others use "3rd digit is large" rule (fontconfig, obby, gobby, sobby, net6 use .90 and higher). Still others label their development releases "alpha", "beta", or "rc" (php5). Once you know how they label their development versions, you can fix the livecheck to skip those versions. I fixed soprano's livecheck in r61410 using a version of the one from fontconfig.