.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
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 tr
auto-connect our themes, other platforms would likely
want to auto-connect some others?
[1] https://github.com/ubuntu/snapcraft-desktop-helpers/pull/30
Cheers,
--
Michał Sawicz
Canonical Ltd.
signature.asc
Description: OpenPGP digital signature
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
ds like we'd need the ability to connect to multiple theme snaps and
then have the user's environment choose the right one?
Is it even possible to plug into multiple slots?
--
Michał Sawicz
Canonical Ltd.
signature.asc
Description: OpenPGP digital signature
--
Snapcraft
t it originally was when the snap is removed?
> That sounds like the justification behind a feature request for an
> uninstall hook: https://bugs.launchpad.net/snapd/+bug/1661126 .
Shouldn't that get cleaned up on daemon stop in this case, though?
--
Michał Sawicz
Canonical Ltd
