Hi Dmitry,
> Thank you, Sergey. Does incompatibility goes other way too, that version
> without LFS support is incapable of reading file, created with LFS
> version?
Yes, as the accompanying NOTE-WARNING file says:
Gdbm files have never been `portable' between different operating
systems, system architectures, or potentially even different compilers.
Differences in byte order, the size of file offsets, and even structure
packing make gdbm files non-portable.
(btw, this file seems not to be included in the Debian package, perhaps
it makes sense to do so).
> I consider providing statically-linked, LFS-disabled version of
> gdbm_{load,dump,tool}, so user with database, created on stretch could
> do `gdbm_dump old.gdbm | gdbm_load new.gdbm'. Opinions?
That's nice idea. I'm all for it.
Best regards,
Sergey
