parts
Revision 151 as of 2018-02-26 23:42:58
Clear message
--- origin: https://github.com/diddledan/snapcraft-alsa.git maintainer: Daniel Llewellyn <diddledan@ubuntu.com> description: ALSA part for snapcraft, which will compile ALSA and install a loader script which redirects audio through pulseaudio without requiring the `alsa` plug to be connected manually or by store assertion. See README.md on github.com/diddledan/snapcraft-alsa.git for more details parts: [alsa, alsa-lib, alsa-plugins] --- origin: https://github.com/popey/nwjs-support.git maintainer: Alan Pope <alan.pope@canonical.com> description: nwjs-support is a part which pulls in the necessary pieces to support an nwjs application as snaps parts: [nwjs-support] --- origin: https://github.com/sergiusens/patchelf-snap.git maintainer: Sergio Schvezov <sergio.schvezov@canonical.com> description: PatchELF is a simple utility for modifying existing ELF executables and libraries. In particular, it can do the following, * Change the dynamic loader ("ELF interpreter") of executables. * Change the RPATH of executables and libraries. * Shrink the RPATH of executables and libraries. * Remove declared dependencies on dynamic libraries (DT_NEEDED entries). * Add a declared dependency on a dynamic library (DT_NEEDED). * Replace a declared dependency on a dynamic library with another one (DT_NEEDED). parts: [patchelf] --- origin: https://github.com/mariogrip/openssh.git maintainer: Marius Gripsgard <mariogrip@ubuntu.com> description: OpenSSH is the premier connectivity tool for remote login with the SSH protocol. It encrypts all traffic to eliminate eavesdropping, connection hijacking, and other attacks. In addition, OpenSSH provides a large suite of secure tunneling capabilities, several authentication methods, and sophisticated configuration options. parts: [openssh] --- origin: https://github.com/dplanella/qt5conf.git maintainer: David Planella <dpm@ubuntu.com> description: This sets up qt5.conf for projects using qml and other qt5 components that need an Ubuntu standard internal path setup by default like the Ubuntu Core Apps. parts: [qt5conf] --- origin: https://github.com/kyrofa/qt4conf.git maintainer: Kyle Fazzari <kyle@canonical.com> description: This sets up qt4.conf for projects using qml and other qt4 components that need an Ubuntu standard internal path setup by default like the Ubuntu Core Apps. parts: [qt4conf] --- origin: https://github.com/dplanella/gtkconf.git maintainer: David Planella <dpm@ubuntu.com> description: This sets up the GTK environment for GTK-based projects parts: [gtkconf] --- origin: https://github.com/sergiusens/curl.git maintainer: Sergio Schvezov <sergio.schvezov@ubuntu.com> description: A tool and a library (usable from many languages) for client side URL transfers, supporting FTP, FTPS, HTTP, HTTPS, TELNET, DICT, FILE and LDAP. parts: [curl] --- origin: https://github.com/sergiusens/mqtt-paho.git maintainer: Leo Arias <leo.arias@canonical.com> description: mqtt-paho for python. parts: [mqtt-paho-python2, mqtt-paho-python3] --- origin: https://github.com/sergiusens/mqtt-paho.git maintainer: Leo Arias <leo.arias@canonical.com> description: mqtt-paho for python. parts: [mqtt-paho/python2, mqtt-paho/python3] --- origin: https://github.com/Winael/ffmpeg.git maintainer: Winael <vinzjobard@ubuntu.com> description: This sets up ffmpeg for projects. parts: [ffmpeg] --- origin: git://kernel.ubuntu.com/hwe/fwts.git origin-type: git maintainer: Firmware Testing Team <fwts-devel@lists.ubuntu.com> description: This sets up fwts for projects. parts: [fwts] --- origin: https://github.com/ubuntu/snapcraft-desktop-helpers.git maintainer: Snapcraft community (https//forum.snapcraft.io) description: | Helpers for gtk2, gtk3, qt4 and qt5 or gnome-platform and glib minimal launchers. It brings the necessary code and exports for binding and using those desktop technologies in a relocatable fashion, enabling binding with global desktop theme, icon theme, image caching, fonts, mimetype handlers application global menu and gsettings integration. It also brings basics ubuntu dependency packages. . Usage: 1. add "after: [desktop-<technology>]" to your launcher: - gtk2, gtk3, qt4 and qt5 corresponds to their respective toolkit main dependencies and default choices. - gnome-platform is similar to gtk3 without the extra depends, it's meant to be used with the gnome platform which already includes those. - glib-only enables to compile mime types and gsettings infos. If you added your own graphical drivers, it will link them as well. 2. prepend your command with "desktop-launch", like: commands: "desktop-launch foo" if foo is in $PATH. You can as well specify: "desktop-launch $SNAP/foo". 3. add needed plugs to your application: - for graphical application: plugs: [x11 (or unity7 for appmenu integration)]. Think about adding opengl if you need hw acceleration. - if your application needs access to sound: plugs: [pulseaudio] - accessing to user's home directory: plugs: [home] - read/write to gsettings: plugs: [gsettings] - use of the shared platform snap content, first define the plug: plugs: gnome-3-26-1604: interface: content target: gnome-platform default-provider: gnome-3-26-1604:gnome-3-26-1604 and then make your apps use it: plugs: [gnome-3-26-1604] Note that an empty "gnome-platform" directory will be created for you in your snap. parts: - desktop-gtk2 - desktop-gtk3 - desktop-qt4 - desktop-qt5 - desktop-glib-only - desktop-gnome-platform --- #origin: https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/tpm origin: https://git.launchpad.net/~joetalbott/snappy-hwe-snaps/ origin-type: git maintainer: Canonical System Enablement <snapcraft@lists.snapcraft.io> description: Part containing utilities to interact with a TPM chip being part of a computer system. parts: [tpm-tools] --- origin: https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/tpm2 origin-type: git maintainer: Canonical System Enablement <snapcraft@lists.snapcraft.io> description: Part containing utilities to interact with a TPM 2.0 chip being part of a computer system. parts: [tpm2-tools] --- origin: https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/tpm2 origin-type: git maintainer: Canonical System Enablement <snapcraft@lists.snapcraft.io> description: Implementation of the TPM 2.0 Software Stack (TSS). See https://github.com/01org/TPM2.0-TSS for the upstream project provided by this part and https://code.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/tpm2/ for the actual source code of this part. parts: [tpm2-tss] --- origin: https://git.launchpad.net/~checkbox-dev/checkbox/+git/checkbox-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: Part that supplies the latest stable version of the Checkbox tools for certifying devices. Fetches packages from PyPI. parts: [checkbox] --- origin: https://git.launchpad.net/~checkbox-dev/checkbox/+git/checkbox-dev-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: Part that supplies the latest stable version of the Checkbox tools for certifying devices. Fetches sources from git repositories. parts: [checkbox-support-dev, checkbox-ng-dev, checkbox-dev] --- origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-snappy/+git/plainbox-provider-snappy-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: Tests to certify the correct functioning of devices running releases of snappy Ubuntu Core parts: [plainbox-provider-snappy] --- origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-checkbox/+git/plainbox-provider-checkbox-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: This part contains the CheckBox jobs collection, i.e the hardware test definitions and scripts originally included with CheckBox parts: [plainbox-provider-checkbox] --- origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-resource/+git/plainbox-provider-resource-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: Resource jobs are that are used to gather information about a system prior to running to the running plainbox-provider-snappy test suite parts: [plainbox-provider-resource] --- origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-certification-server/+git/plainbox-provider-certification-server-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: Test plans that are used as part of the Server Certification programme parts: [plainbox-provider-certification-server] --- origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-certification-client/+git/plainbox-provider-certification-client-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: Test plans that are used as part of the Client Certification programme parts: [plainbox-provider-certification-client] --- origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-sru/+git/plainbox-provider-sru-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: Test plans that are executed as part of kernel SRU cycles parts: [plainbox-provider-sru] --- origin: https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager origin-type: git maintainer: Canonical System Enablement <snapcraft@lists.snapcraft.io> description: | Part providing access to the NetworkManager client utilities namely nmcli but this part also provides the NetworkManager service binary as well. parts: [networkmanager] --- origin: https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/modem-manager origin-type: git maintainer: Canonical System Enablement <snapcraft@lists.snapcraft.io> description: | Part providing access to the ModemManager client utilities namely mmcli but this part also provides the ModemManager service binary as well. parts: [modemmanager, libmbim, libqmi] --- origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-ipdt/+git/plainbox-provider-ipdt-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: Tests to certify the correct functioning of devices running releases of snappy Ubuntu Core with Intel Processors parts: [plainbox-provider-ipdt] --- origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-docker/+git/plainbox-provider-docker-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: Tests to certify the correct functioning of Docker containers running on releases of snappy Ubuntu Core parts: [plainbox-provider-docker] --- origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-tpm2/+git/plainbox-provider-tpm2-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: Tests to certify the correct functioning of TPM2 devices parts: [plainbox-provider-tpm2] --- origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-snappy/+git/parts-meta-info origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: This part if included in the snap will generate 'parts_meta_info' file in the snaps root directory containing information about the revisions used in each part of the snap. parts: [parts-meta-info] --- origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-snappy/+git/plainbox-provider-engineering-tests-parts origin-type: git maintainer: Checkbox Developers <checkbox-devel@lists.ubuntu.com> description: Plainbox provider with Engineering Tests parts: [plainbox-provider-engineering-tests] --- origin: https://github.com/jocave/simple-make-filesets.git origin-type: git maintainer: Jonathan Cave <jonathan.cave@canonical.com> description: The filesets test from the integration test suite. parts: [simple-make-filesets] --- origin: https://github.com/evandandrea/mongodb-part.git maintainer: Evan <ev@ubuntu.com> description: A document-oriented database parts: [mongodb] --- origin: https://github.com/lool/dnsmasq-snap.git maintainer: Loïc Minier <loic.minier@ubuntu.com> description: Network infrastructure swiss-army knife parts: [dnsmasq] --- origin: https://github.com/cpaelzer/waf-snapcraft.git origin-type: git maintainer: Christian Ehrhardt <christian.ehrhardt@canonical.com> description: Waf c Demo parts: [wafdemo] --- origin: https://github.com/tjyrinki/qt57.git origin-type: git maintainer: Timo Jyrinki <timo-jyrinki@ubuntu.com> description: | Qt 5.7 part (upstream). Lets you use newer Qt than what is available in Ubuntu, although by compiling it as a part before your application. This takes a lot of time. WIP. See use example at: https://github.com/tjyrinki/timostestapp2 or install "timostestapp2" from Snap store edge channel. You will need the plugins, and the launcher and modify it and snapcraft.yaml as needed. parts: [qt57] --- origin: https://github.com/tjyrinki/qt58.git origin-type: git maintainer: Timo Jyrinki <timo-jyrinki@ubuntu.com> description: | Qt 5.8 part (upstream). Lets you use newer Qt than what is available in Ubuntu, although by compiling it as a part before your application. This takes a lot of time. WIP. See also the use example of qt57 part, you'll need the overriding plugins. parts: [qt58] --- origin: https://git.launchpad.net/~swem/+git/librealsense-part origin-type: git maintainer: Chen-Han Hsiao (Stanley) <stanley.hsiao@canonical.com> description: Intel® RealSense™ Cross Platform API parts: [librealsense] --- origin: https://github.com/3v1n0/appindicators-snapcraft-parts.git maintainer: Marco Trevisan <marco@ubuntu.com> description: | Parts to show app-indicators for gtk2, gtk3, qt4 and qt5. . Usage: 1. add "after: [indicator-<technology>]" to your part: - gtk2, gtk3, qt4 and qt5 corresponds to their respective toolkit. main dependencies and default choices. 2. add 'unity7' plug to your application parts: - indicator-qt4 - indicator-qt5 - indicator-gtk2 - indicator-gtk3 - indicator-qt4-from-src - indicator-qt5-from-src - indicator-gtk2-from-src - indicator-gtk3-from-src --- origin: https://github.com/sergiusens/snapcraft-preload.git maintainer: Sergio Schvezov <sergio.schvezov@ubuntu.com> description: | Tired of dealing with hardcoded paths and code just being antiquated? This is the part for you. While still in experimental stages it is useful already. All you need to do is add this part to your snapcraft project and prepend `command` entries in `apps` with `snapcraft-preload`. parts: [snapcraft-preload, preload] # XXX: This needs to be updated because it references no-longer-existing desktop-ubuntu-app-platform part. #--- #origin: https://gitlab.com/mardy/snapcraft-webapp-helper.git #maintainer: Alberto Mardegan <alberto.mardegan@canonical.com> #description: | # Helper for webapps. # It brings the webapp-container program and makes use of the # ubuntu-app-platform snap. #parts: [webapp-helper] # XXX: this origin needs a link from snap/snapcraft.yaml to snapcraft.yaml until the parser # is fixed to support snap/snapcraft.yaml. https://bugs.launchpad.net/snapcraft/+bug/1665007 # Joe Talbott <joe.talbott@canonical.com> 2017-02-15 # - - - #origin: https://github.com/juju/juju.git #origin-depth: 1 #maintainer: Nicholas Skaggs <nicholas.skaggs@canonical.com> #description: | # Juju part #parts: [juju] --- origin: https://github.com/lxc/lxd-pkg-ubuntu.git origin-branch: snappy-16 maintainer: LXD Developers <lxc-devel@lists.linuxcontainers.org> description: | Parts for LXD parts: [lxd, lxc, lxcfs] --- origin: https://github.com/ubuntu/simple-webserver-part.git maintainer: Didier Roche <didier.roche@canonical.com> description: | Simple webserver part In your snapcraft.yaml, just have one of your snapcraft part defining: `after: [simple-webserver]` Then, spawn a service with it, with the part relative to your snap to serve: apps: my-server: command: webserver www daemon: simple restart-condition: always plugs: [network-bind] Here, `www` is relative to $SNAP from your own snap. You can change the default port (8080) with the -p option, for instance: parts: [simple-webserver] --- origin: https://github.com/elopio/go.git maintainer: Leo Arias <leo.arias@canonical.com> description: | Go is an open source programming language that makes it easy to build simple, reliable, and efficient software. This snapcraft part allows to build programs written in go. Usage: Add "after: [go]" to your part written in go. This will use the latest go from the master branch to compile your program. If you want to specify a go version, also add a go part with the version as the source-tag value. For example, to use go 1.7.5, use: parts: my-go-program: ... after: [go] go: source-tag: go1.7.5 parts: [go] --- origin: https://github.com/mhall119/tomcat-snap-part.git maintainer: Michael Hall <mhall119@ubuntu.com> description: | Makes it easy to build a snap for a Java/J2EE webapp running on top of Apache Tomcat Usage: To use this part, include the following in your snapcraft.yaml: apps: my-app: command: tomcat-launch daemon: simple plugs: [network-bind] parts: my-webapp: source: http://example.com/my-webapp.tar.gz plugin: dump organize: my.war: webapps/my.war after: [tomcat] All you need is to put your war file into the ./webapps/ directory, and the Tomcat part will take care of the rest, starting a daemon on port 8080 running your app. parts: [tomcat] --- origin: https://github.com/bsutton/tomcat-with-ssl-snap.git maintainer: Brett Sutton <bsutton@noojee.com.au> description: | Add tomcat-with-ssl to your snap to enable SSL on port 443 for tomcat (no apache required). Lets Encrypt's 'certbot' is used to obtain a valid certificate. Tomcat exposes port 443 directly so there is no need to add apache or ngnix as a proxy. After installing your snap you need to run <yoursnapname>.getcert <youremail> <fqdn-of-webapp> Your server MUST have port 80 exposed when you run get cert and you must have an public DNS entry for the FQDN of your web server. Additional documenation at: https://github.com/bsutton/tomcat-with-ssl-snap Usage: To use this part, include the following in your snapcraft.yaml: apps: tomcat: command: tomcat-launch daemon: simple plugs: [network, network-bind] # used to ran the certbot renewal process. cron: command: cron daemon: simple plugs: [network, network-bind] getcert: command: getcert plugs: [network, network-bind] parts: # build the web app orion-monitor-webapp: plugin: maven source: git@bitbucket.org:sbsutton/orionmonitor.git maven-options: [-DskipTests=true] organize: war/orionmonitor-1.0-SNAPSHOT.war : webapps/orionmonitor.war after: [tomcat-with-ssl] --- origin: https://github.com/lirios/snapcraft-parts.git maintainer: Tim Süberkrüb <dev@timsueberkrueb.io> description: | Cloud parts for snap packages depending on the Liri Platform snap. The Liri Platform cloud parts contain a specific launcher and Snapcraft configuration to deduplicate build configurations. parts: - liri-platform-0-9 --- origin: https://github.com/RevTwoInAppSupport/linux-agent.git maintainer: Jim Hansen <jim@revtwo.com> description: | Part for Revtwo agent for remote support of linux devices parts: [rev2agent] --- origin: https://github.com/msis/moos-ivp-snap-parts.git maintainer: Mohamed Saad Ibn Seddik <ms.ibnseddik@gmail.com> description: | MOOS-IvP Marine Autonomy suite parts: [moos-ivp] --- origin: https://github.com/kyrofa/snap-arch-triplet-generator.git maintainer: Kyle Fazzari <kyrofa@ubuntu.com> description: | Turn $SNAP_ARCH into $SNAP_ARCH_TRIPLET. Simply launch your app with with_snap_arch_triplet <app>. parts: [snap-arch-triplet-generator] ---