![]() ![]() ![]() * `snapcraft clean` is a convoluted cli to manage states for parts. We need to urgently improve the experience of people re-running stages, as this is foundation of the try-and-run cycle. To recover from this state I had to nuke the parts/qt5conf path, which is not intuitive. '/home/ niemeyer/ src/makemkv/ snap/bin/ qt5-launch' Instead of taking the cue that the directory is simply not there, snapcraft barfs on internal state: This is the most obvious way to "clean" when one really cannot tell snapcraft what to do. 'snap' is not a valid step for part 'qt5-packages' Right now it skips if it was already done before, which is a fine behavior when a part name is not given, but when the developer requested a specific part, it should actually respect the request rather than assuming a cached result is okay. If one types "snapcraft build some-part", this should indeed build the part. Several small nits that come in mind right now:ฤก. When using snapcraft in practice I've been often stumbling upon the behavior of "cleaning". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |