Well... I'm still waiting for the answer from upstream, but if you are right (and I fear you are) changing the behaviour would break other applications, and I do not believe that this would be wise.
Moreless we would need an migration path, like patching tokyocabinet to automatically detect endianess and act accordingly (whatever this is; for sure this is not a trivial thing ) So lets wait for an answer from upstream before looking into detailed options, but currently I cannot rule out to tag this "won't fix" or at least "help-needed". Tobias Am Montag, den 09.04.2012, 22:09 +0200 schrieb Mikhail Gusarov: > Hi. > > Upstream Tokyo Cabinet uses little-endian data in databases and hence > the databases are portable. > > After disabling the switch database format will not change for > big-endian machines, but *will* for little-endian ones, so existing > databases on little-endian machines will become unreadable and opening > those will fail with "invalid metadata" error. > > BTW, I stand corrected in the original bug report: on big-endian > machines database format is correct. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
