Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
languages: add MOOS guide #131
Conversation
| + | ||
| +## Getting started | ||
| + | ||
| +Let's take a look at ping/pong MOOS example application, and show how simple it is to snap. |
| + | ||
| +You can [extend the behaviour](/build-snaps/scriptlets) of any part in your `snapcraft.yaml` with shell commands. These can be run after pulling the source code but before building by using the `prepare` keyword. The build process can be overridden entirely using the `build` keyword and shell commands. The `install` keyword is used to run shell commands after building your code, useful for making post build modifications such as relocating build assets. | ||
| + | ||
| +For example, let's pretend that the MOOS examples contained a suite of tests (they don't, so this won't actually work). We could run that test suite at the end of the build. If these tests failed, the snap creation would be terminated: |
evandandrea
Oct 4, 2017
Collaborator
Is there really no functional example we can give for scrollers? It’s weird to say “don’t try this, it won’t work.”
kyrofa
Oct 4, 2017
Collaborator
I'm afraid not. This is the best pre-baked example we have, and it doesn't even have install rules much less tests
evandandrea
Oct 4, 2017
Collaborator
Are MOOS developers likely to need scriplets? If not, I’d drop it. If they are, well, it doesn’t have to be tests.
kyrofa
Oct 4, 2017
•
Edited 1 time
-
kyrofa
Oct 4, 2017
Collaborator
-
Oct 4, 2017
Not necessarily, the best example is to run their own tests. I'll go ahead and drop this section, at least for now. We can add it back if we come up with a brilliant idea.
kyrofa
added some commits
Oct 4, 2017
|
We’ll need a PR to link to it, but let’s get this landed |
evandandrea
merged commit 7798c42
into
canonical-docs:master
Oct 4, 2017
|
well... that was quick ;-) should I still read through this? |
kyrofa commentedOct 4, 2017
My take of the user-story-driven docs for MOOS developers.