This manifest file would be interesting for more than just the core snap-- it would be useful for app snaps and really anything that uses stage-packages since the manifest could then be examined for out-of-dateness of staged packages. This seems like it would be useful for more than just Launchpad builds and seems like snapcraft should handle it itself (AIUI, the Launchpad buildds use snapcraft to build snaps). Am I missing something?

El 09/08/16 a las 12:40, Jamie Strandboge escribió:
> This manifest file would be interesting for more than just the core
> snap-- it would be useful for app snaps and really anything that uses
> stage-packages since the manifest could then be examined for out-of-
> dateness of staged packages. This seems like it would be useful for more
> than just Launchpad builds and seems like snapcraft should handle it
> itself (AIUI, the Launchpad buildds use snapcraft to build snaps). Am I
> missing something?
>
Yes, we already have a bug for that ;-)

This is the manifest produced by live-build wrapped inside a part which is totally disconnected from snapcraft itself.

no, you are right, LP uses snapcraft ... but there is also code in launchpad-buildd missing to publish them currently ... for my usecase i agreed with colin to actually just make my build spit out a .manifest in the toplevel build dir next to the snap ... but that indeed only works when using a tool that creates these files so yes, i think it would make sense if snapcraft itself could also create them.