On Monday 16 May 2016 14:21:07 Martin Steigerwald wrote: > Hello Richard, > > On Montag, 16. Mai 2016 13:14:56 CEST Richard W.M. Jones wrote: > > I don't have time to implement this right now, so I'm just posting > > this as a suggestion/request ... > > > > It would be really helpful if the btrfs tools had a machine-readable > > output. > > > > Libguestfs parses btrfs tools output in a number of places, eg: > > https://github.com/libguestfs/libguestfs/blob/master/daemon/btrfs.c > > This is a massive PITA because each time a new release of btrfs-progs > > comes along it changes the output slightly, and we end up having > > to add all sorts of hacks. > > > > With machine-readable output, there'd be a flag which would > > change the output. eg: > > I wonder whether parsing a text based output is really the most elegant method > here. > > How about a libbtrfs so that other tools can benefit from btrfs tools > functionality? btrfs-progs is GPL v2 only, and that may be an issue for consumers (the libguestfs daemon, the component interacting with devices and filesystems inside the libguestfs appliance, is GPL v2+ for example). > Of course it would likely me more effort than to implement structured output. There's this of course, which is not entirely negligible. -- Pino Toscano
Attachment:
signature.asc
Description: This is a digitally signed message part.
