From: Jared McIntyre (jmcintyre_at_[hidden])
Date: 2007-06-19 10:34:03
Robert Ramey <ramey <at> rrsd.com> writes:
> Jared McIntyre wrote:
> > So, my problem is that we need to move to Boost 1.34, but I need a
> > serialization library that interoperates with 1.33 serialization. I
> > could hack my code to post-process the file, but it would be ugly.
> Hmmm - If you're going to generate new data files and distribute
> them to be processed with the old binaries - why can't you distribute
> the new binaries at the same time?
> Robert Ramey
I can't get into the special way that our software is release/delivered, so
you'll have to trust me when I say that would add 2-3 months of testing
time to do it. I won't be able to get management to okay that for this
change. We will probably do it in about a year, but we would like to be
using Boost 1.34 between now and then, and the only reason that won't
work is that some of the serialized files that are shared between
sub-releases are serialization version 3 (binaries are not reused across
sub-releases, so for a sub-release that uses 1.33, it is all 1.33, and so
forth -- no risk of binary incompatibilities). So I'm trying to come up with
a workaround so that these two sets of sub-releases can use the one
serialization file shared between them.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk