|
|
471.
|
|
|
The build you uploaded is now the selected revision in the stable channel, meaning that installs of your snap will select this upload by default.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../create/index.html
|
|
|
472.
|
|
|
Recap
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../create/index.html
|
|
|
473.
|
|
|
prime/command-hello-service.wrapper
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../create/index.html
|
|
|
474.
|
|
|
commands come from:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../create/index.html
|
|
|
475.
|
|
|
command is shorthand for the real command, which is
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../create/index.html
|
|
|
476.
|
|
|
$ snapcraft list-plugins ant copy kernel nodejs tar-content autotools go make python2 catkin jdk maven python3 cmake kbuild nil scons
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../create/index.html
|
|
|
477.
|
|
|
The revision for a snap is unique. In this example, because you built the snap locally, it gets a local alphanumeric revision that is unique on this machine only. When you load a snap from the store, the revision is an integer number that exactly identifies the snap that is installed. While you can't do this for local revisions, with snaps loaded from the store you can compare revisions on two machines to determine if they have exactly the same content installed.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../create/index.html
|
|
|
478.
|
|
|
In some trees it may be preferable to name the snapcraft YAML file
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../create/index.html
|
|
|
479.
|
|
|
Each stage of the tour is in a separate subdirectory, with number prefixes showing the sequence. In each directory you'll find a README with the instructions from this page relevant to that directory, so you don't need to continually switch between the browser and your terminal as you follow the tour.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../create/index.html
|
|
|
480.
|
|
|
/build/ Note that plugins might well define their own semantics for the 'source' keywords, because they handle specific build systems, and many languages have their own built-in packaging systems (think CPAN, PyPI, NPM). In those cases you want to refer to the help text for the specific plugin. snapcraft help
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../create/index.html
|
