This is one area that is still super confusing, and would be worth investing some time on soon.
We discussed this back in May on: - clean behavior is confusing https://bugs.launchpad.net/snapcraft/+bug/1582469 As described there, this is a rock on the most important pipeline of the tool. On Mon, Jan 9, 2017 at 11:31 PM, Kyle Fazzari <[email protected]> wrote: > On 01/09/2017 12:08 PM, Michał Sawicz wrote: > > W dniu 09.01.2017 o 20:32, Michał Sawicz pisze: > >> I *think* (may be wrong) that `snapcraft pull` can help here: > >> > >> http://snapcraft.io/docs/reference/snapcraft-command#pull > > > > I was able to force `snapcraft pull` to pull things again by messing > > with parts/part-name/state - might wanna try that in case there's no > > better answers. > > Careful with this, snapcraft tends to get upset if you mess with its > state behind its back. > > Lifecycle steps build upon each other: pull -> build -> stage -> prime. > Let's say you ran `snapcraft build A`, which will pull part A (let's say > it was commit abdc1), and then build it. If commit abcd2 is later made > and you want to build it, you need to clean the pull step (which will > also clean the build step) with `snapcraft clean A`, and build again: > `snapcraft build A`. That will pull any updates that have been made, and > build anew. > > -- > Kyle Fazzari (kyrofa) > Software Engineer > Canonical Ltd. > [email protected] > > > -- > Snapcraft mailing list > [email protected] > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/snapcraft > > -- gustavo @ http://niemeyer.net
-- Snapcraft mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
