Skip to content

Commit

Permalink
Use full adapter instead
Browse files Browse the repository at this point in the history
Signed-off-by: 林博仁(Buo-ren Lin) <Buo.Ren.Lin@gmail.com>
  • Loading branch information
brlin-tw committed Mar 6, 2019
1 parent e3322a6 commit b35da68
Showing 1 changed file with 8 additions and 6 deletions.
14 changes: 8 additions & 6 deletions snap/snapcraft.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -99,12 +99,14 @@ grade: stable
# via `_snap_name_._app_name_` or `snap run _snap_name_._app_name_`
apps:
hello-snapcrafters:
# The command to run the application, the base command should be an *relative path* to an executable file rooted from the `prime` directory (for `classic` confinement compatiblity, where command search PATHs under $SNAP isn't set for library compatiblity reasons). The arguments are usually other launchers' *absolute path* rooted from the $SNAP environment variable that are *stacked over* previous ones to consolidate their runtime environment modifications.
# NOTE: The right angle bracket at the beginning of the value of the `command` keyword starts a YAML folded style block scalar, refer the following spec document for more info: http://yaml.org/spec/1.2/spec.html#id2796251
command: >
bin/hello-launch
"${SNAP}"/bin/locales-launch
"${SNAP}"/bin/hello-snapcrafters
# The environment adapter style to use, `command-chain` is only supported by the `full` adapter
adapter: full

# The command to run the application, the value should be a *relative path* to an executable file rooted from the `prime` directory
command: bin/hello-snapcrafters
command-chain:
- bin/locales-launch
- bin/hello-launch

# If the providing part of the app. has a desktop entry, specify its path relative to the `prime` directory.
# If the packaging target doesn't provide a desktop entry, ignore the `desktop` key and implement a desktop entry in `/snap/gui`
Expand Down

0 comments on commit b35da68

Please sign in to comment.