[sos-devel] sosreport manifest?

[Bryn M. Reeves]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/09/2012 08:32 PM, Mike Clark wrote:
> Hey folks,
> 
> Bryn, I have basically the same question as Jesse here.  But, let
> me go a step further.  If the manifest is to "support the eventual
> creation of a library and language bindings to provide uniform
> access to the data," we really should start with that first.  I
> don't think we even need to consider a manifest until the other
> conversation takes place.

So, my problem here is getting the users of the data to engage with
the team working on sos (and any future access library). I've been
trying to get requirements for downstream data users for the best part
of a year but discussions have never come to anything particularly
concrete.

We need to get something done here as soon as possible - there is
already a proliferation of code to access the data in an sosreport on
a variety of languages. If we find ourselves wanting to make the kind
of changes that we want in sos this is bound to lead to resistance
because this code is very brittle (hard-coded paths are the norm).

By having an answer as to how an external user of the data can
discover the content of a tarball (without resorting to path crawling)
we make a step towards that aim.

I don't think we need anything fancy here, just a journal of what has
been collected and where it is.

Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9d2osACgkQ6YSQoMYUY96hQgCg0REEkSnbOo/cxq5Qu4UwMkHO
/B0AoN0jx3xRshn7LIkxbJM/jmzxsGI9
=3RPY
-----END PGP SIGNATURE-----