On Apr 07, 2017, at 12:37 AM, Steve Langasek wrote:
>That would suffice. It might be nice to do some basic transformations here,
>to make the manifest tabular - à la
Is this file primarily for human or machine consumption?
>I think I would prefer it be written by default to the output dir under a
>fixed name (and if not using -O, to write it out as <foo>.manifest alongside
><foo>.img). It's a cheap enough thing to create, and common enough to want,
>that I think we should just do it as the sensible default thing instead of
>requiring the user to ask for it. If they don't want it, it's a pretty
>cheap file to clean up.
We can do that. Let's be careful though because the file won't contain a
complete manifest of the image, but only a manifest of the snaps. .svm seems
to be unused-ish (snap version manifest).
On Apr 07, 2017, at 12:37 AM, Steve Langasek wrote:
>That would suffice. It might be nice to do some basic transformations here,
>to make the manifest tabular - à la
Is this file primarily for human or machine consumption?
>I think I would prefer it be written by default to the output dir under a
>fixed name (and if not using -O, to write it out as <foo>.manifest alongside
><foo>.img). It's a cheap enough thing to create, and common enough to want,
>that I think we should just do it as the sensible default thing instead of
>requiring the user to ask for it. If they don't want it, it's a pretty
>cheap file to clean up.
We can do that. Let's be careful though because the file won't contain a
complete manifest of the image, but only a manifest of the snaps. .svm seems
to be unused-ish (snap version manifest).
https:/ /en.wikipedia. org/wiki/ List_of_ filename_ extensions_ (S%E2%80% 93Z)#S
% mimetype foo.svm
foo.svm: