Add a new osinfo-db-import tool which takes an archive in the
tar (pax) format, with XZ compression and can extract its contents
into one of the standard libosinfo database locations.
This makes it easy for users to download new copies of the
database and unpack them in the right place.
eg
$ os
Since we're soon going to start distributing the database as a
standalone archive, it'll be useful if we had tools which can
import/export between the local database filesystem tree and a
database archive file. While users/apps could just use 'tar'
directly, providing these tools makes life simpler
Add a new osinfo-db-export tool which creates an archive in the
tar (pax) format, with XZ compression and can filling it with the
database files from one of the standard libosinfo database locations,
or a custom directory.
This makes it easy for users to create their own local custom database
cont
Christophe,
On Wed, Jun 8, 2016 at 12:01 PM, Christophe Fergeau wrote:
> Hey,
>
> Here are fixes for all the leaks I could find when running our test suite
> through valgrind. The last patch does not fix a leak, and is probably not
> strictly required.
ACK all the series, including the last one,
