parts

Revision 97 as of 2017-02-15 15:37:05

Clear message

---
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: https://github.com/ubuntu/snapcraft-desktop-helpers.git
maintainer: Snapcraft community <snapcraft@lists.snapcraft.io>
description: |
  Helpers for gtk2, gtk3, qt4 and qt5 or 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.
       - 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, home]
         (note that the home plug is needed to read new value)
parts:
  - desktop/gtk2
  - desktop/gtk3
  - desktop/qt4
  - desktop/qt5
  - desktop/glib-only
---
origin: https://github.com/ubuntu/snapcraft-desktop-helpers.git
maintainer: Snapcraft community <snapcraft@lists.snapcraft.io>
description: |
  Helpers for gtk2, gtk3, qt4 and qt5 or 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.
       - 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, home]
         (note that the home plug is needed to read new value)
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-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: [plainbox-dev, 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, plainbox-provider-stress-tests, pyalsaaudio]
---
origin: https://git.launchpad.net/~checkbox-dev/plainbox-provider-snappy/+git/plainbox-provider-snappy-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-snappy-resource]
---
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://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://github.com/ubuntu/snapcraft-desktop-helpers.git
maintainer: Timo Jyrinki <timo-jyrinki@ubuntu.com>
description: |
  Helpers for qt5 minimal launchers. This one is for ubuntu-app-platform,
  which corresponds to the shared platform snap use in an easier way than 
  what the older example (https://github.com/tjyrinki/timostestapp3) does.

  An example of usage of the shared platform content can be found at:
  https://code.launchpad.net/~timo-jyrinki/+junk/uitk-gallery

  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-ubuntu-app-platform]" to your launcher:
    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, home]
         (note that the home plug is needed to read new value)
       - use of the shared platform snap content, first define the plug:
           plugs:
             platform:
               content: ubuntu-app-platform1
               default-provider: ubuntu-app-platform
               interface: content
               target: ubuntu-app-platform
         and then make your apps use it:
           plugs: [platform]
parts: [desktop-ubuntu-app-platform]
---
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
---
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 `preload`.
parts: [preload]
---
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]
---