[Please don't CC me in replies. I read lists I write to. Also, please don't cross-post.]
On Wed, Jul 16, 2008 at 02:34:33PM -0700, Adam Williamson wrote: > Why did synce-hal get versioned 0.2, out of sync with all other > components? Because the author versioned it originally 0.1. 0.2 is a clear progression from 0.1. > I packaged it from SVN before any release was made, and assumed 0.11.1 > for the version (figuring the first official release would be 0.12 or > 0.13 or whatever the rest of synce was at at the time). Now if I want to > package this stable release I'll have to use an Epoch tag, which is > excessively ugly and avoided wherever possible. This was a mistake on your part. There is nothing to say that every SynCE module will have exactly the same version number. pywbxml and librtfcomp have different version numbers, for example. You will have to use an epoch tag. > I don't suppose there's any chance it could be re-versioned 0.12? No. I'll change it for the next release so it's in sync with the other modules but this really isn't my problem. -- Jonny Lamb, UK [EMAIL PROTECTED] http://jonnylamb.com GPG: 0x2E039402
signature.asc
Description: Digital signature
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ SynCE-Devel mailing list SynCE-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synce-devel
