Re: support for dumping summary file to plain text form

[Dusty Mabe <dusty dustymabe com>]

On 03/02/2017 09:55 AM, Colin Walters wrote:
> On Wed, Mar 1, 2017, at 11:21 PM, Dusty Mabe wrote:
>
> > 1 teach the command line tools to be able to parse a summary file and
> >   dump it as plain text
>
> Definitely possible, but would require some churn in the C tooling.

would definitely be nice longer term if we don't move to some plain
text based summary file

> > 2 provide a tool that does effectively the same thing
>
> (my PR)

thanks!

> > 3 store the summary file in a plain text, but still machine friendly
> >   form (i.e. json or similar) so that all I need to do is "curl" to
> >   see the details of what is in the file.
>
> We can't change the format of the file now.  We could *add* a new one -
> nothing stops anyone from creating summary.json as well and dropping
> it in the repo if it's viewed as convenient.

so would the potential migration strategy be to have the ostree tools 
look for summary.json and if not there, look for summary (older style)? 

Then we could version the json and make any changes we need to to that
file from there on out? 

> Though really I think this type of thing would best live as a "repo visualizer" app.

visualizers are cool too.