On Sat, Jul 30, 2011 at 08:46:55AM -0000, Parrot wrote: > Downstream in Debian, the upgrade from Perl 5.10 to 5.12 broke Rakudo > compiles, because the installed PMC .dump files were written using the > 5.10 version of Storable, and could not be read using the 5.12 version of > Storable. The upstream bugs (closed) related to this failure are:
I suspect that the problem is that they were written with Storable::store, which is platform and configuration specific, and that when upgrading from 5.10 to 5.12 Debian changed their perl configuration from 32 to 64 bit integers. Storable itself is quite capable of reading files made all the way back to 0.60-something, for the same configuration. Had parrot used Storable::nstore (the slower but portable format) there would not have been this problem. > This is solved in the short-term, but in the longer-term, Storable is not > a good format for installed, persistent metadata. (It was never intended > to be installed, only to be a temporary build-process cache.) However, that's key. As the intent was not to install the files, then the faster "native" format was a sane choice. And I agree with that (any) Storable format isn't an appropriate choice for something installed. It's not a format that parrot itself can read. Nicholas Clark _______________________________________________ parrot-tickets mailing list [email protected] http://lists.parrot.org/mailman/listinfo/parrot-tickets
