The snapcraft update operation is currently described as:
Usage: snapcraft update [OPTIONS]
Updates the parts listing from the cloud.
This is an innocent looking operation, perhaps inspired by “apt-get update” which is mainly a metadata fetching operation. It doesn’t even feel like being aware of containers is something relevant for it. The behavior being proposed on the other hand is more aggressive, and could lead to a snap that doesn’t build anymore because things are changing under it.
Given that it runs “snap refresh”, perhaps “snapcraft refresh” would be the right term for it?
I’m also curious about that first point:
Is there a topic I could read more about the end user experience intended? We already have cleanbuild which builds on a LXD container, so now we have two different ways to do that. Is that a migration towards something else, or do we need to consider where we intend to be eventually?