Comment 1 for bug 2011993

Note, @Sergio suggested earlier this week that I used `snapcraft build --shell; cd parts/workshops/build` and then try to run the commands from the scriptlet manually to try and catch the failure. This almost works... it doesn't actually drop me into the right directory, so after cd'ing to /root/parts/workshops/build, I found that (a) the directory wasn't populated and (b) flutter-elinux wasn't found on my PATH.

What I finally ended up doing was adding:

craftctl default
exit 0

...to my scriptlet, and then running `snapcraft build workshops --shell-after`, which dropped me into the container with a populated build directory, and flutter-elinux found on my PATH.

Of course now when I run all of the flutter-elinux commands by hand, it works. Thanks Murphy.