Here's my situation: Some coworkers and I are working on a unity8-session snap. We have a silo with some fixes and it's connected to a snap recipe that builds the occasional on-demand snap. The snap is supposed to be built with xenial+overlay+silo. I was seeing some inconsistent behavior with other people that built their own snap. And I was seeing inconsistent behavior with other people that downloaded the silo snap. It turns out that snapcraft inserts some LD_LIBRARY_PATH values in the command-*.wrapper scripts based on how the build system is set up. (right?) Those differences between coworkers and the silo meant that some things were broken based on whose snap was being used, despite everything else being the same. Needless to say, that's annoying. Ideally we'd all be building "clean" snaps (as close to silo as possible). There's a "snapcraft cleanbuild" option. I'm not super familiar with it, but I'm guessing it would take some manual work to configure the lxd instance with xenial+overlay+silo. And might be harder to iteratively build too? Another option would be to let us build a snap without the special wrapper sauce? Or maybe just making sure that stage-packages are also used as build-packages (so that the silo build would also know about the extra LD_LIBRARY_PATHs from the system)? I'm not sure what the solution is necessarily. And I'm not even sure I've accurately diagnosed the problem. But the inconsistent experience felt annoying for a packaging format that is supposed to smooth out system differences.