Christopher Browne <[EMAIL PROTECTED]> writes:
> The "lawyering" of this would doubtless be of interest with other
> projects too.
Yeah. We'll see, though it looks like we're probably OK.
> Debian's release of libdb2 comes with "db_dump185", which is rather
> suggestive of a past migration.
>
> I suspect this won't be a _huge_ issue.
Right. We can probably integrate it fairly cleanly, though people who
upgrade across two major format changes might cause trouble.
> If we used a customized sort order, one of the early utilities ought
> to be a custom dump/load, so I don't see this as an immense problem.
Yep. Probably pretty straightforward. In fact it could potentially
just be handled with appropriate arguments to gnucash.
> The format isn't downright nasty (well, if you forget the -d flag,
> it looks pretty nasty...), and is certainly a whole lot better than
> fighting with a binary format.
True, though you might want to try the "-p" option rather than the
"-d" option.
> [Entertaining utility of the month: Bun. It uses the CDB format for
> storage, and essentially replicates cpio/tar's functionality, albeit
> sans compression. The cool part is that since it uses a
> well-specified "hash table" format, it is _trivial_ to write
> programs to walk through data files and look at what's in them. I
> don't think tar or cpio are particularly easy to hack around
> with...]
Interesting. As a bit more trivia, Debian's .deb files are actually
"ar" archives containing files containing the main tar file, the
debian control files (as a tar file), and the debian-binary file...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
