W dniu 08.01.2017 o 20:20, Dalton pisze: > > Is there any way to get Snapcraft to pull the git source of a kernel at > every build without cleaning the entire build directory? > > Currently, if I make a change to my kernel source (I'm using a source in > '.' in my case) then commit it, Snapcraft simply ignores the changes > since it has pulled the source previously, printing 'Skipping pull > kernel (already ran)'. I have to run 'snapcraft clean' in order to get > it to pull the (local) source again. Snapcraft then goes on and > redownloads 'os.snap', a 60MB file, again. On a fast connection, this is > no problem. I'm on a slightly slower connection that also has a data > cap, so this is a waste of both time and bits. > > It seems like there are two ways to avoid this: A way to cache os.snap > locally, or a way to have Snapcraft run 'git pull' to grab source > changes into its working directory. Is either possible right now?
I *think* (may be wrong) that `snapcraft pull` can help here: http://snapcraft.io/docs/reference/snapcraft-command#pull -- Michał Sawicz <michal.saw...@canonical.com> Canonical Ltd.
signature.asc
Description: OpenPGP digital signature
-- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
