MakingPortsAvailable

Differences between revisions 5 and 6
Revision 5 as of 2013-07-31 09:52:24
Size: 3066
Editor: dholbach
Comment:
Revision 6 as of 2013-07-31 12:01:12
Size: 3336
Editor: dholbach
Comment:
Deletions are marked like this. Additions are marked like this.
Line 28: Line 28:
  1. `vi location.json` and put the URL of your image in there. The notation is in JSON format, so do something like this: {{{   1. create `manifest.json` and put the URL of your image in there. The notation is in JSON formatand it has the following values:
   * Image URLs: You will need to provide URLs to images, which don't require any user interaction for downloading. Just pointing `wget` or `curl` at the URL should do the trick. (`goo.im` or `ubuntuone.com` for example.)
    * '''`device`''' (mandatory): it points to the image you're providing.
    * `ubuntu` (optional): the Ubuntu image, by default it's the latest official Ubuntu image.
   * `hash` (optional): hash sum of the current image.
   * `hash_func` (optional): either `md5` or `sha256`.
   * `revision` (optional): provide a revision for the current image.
  Something like this could work: {{{
Line 33: Line 40:
}}}<<BR>>The `device` key is mandatory and points to the image you're providing, the `ubuntu` key is optional and will assume the latest official Ubuntu image.<<BR>> You will need to provide URLs to images, which don't require any user interaction. Just pointing `wget` or `curl` at the URL should do the trick. (`goo.im` or `ubuntuone.com` for example.)<<BR>> Save the file. }}}<<BR>> Save the file.
Line 35: Line 42:
  1. `bzr add license location.json`   1. `bzr add license manifest.json`

Warning /!\ Ubuntu Touch is no longer maintained as a core product by Canonical. However, the Ubports community are continuing development.

This is still a draft! We are working on making this a reality. Current blocker is bug 1201811.

Why?

You want users of a specific device to be able to very easily flash their devices and benefit from the work you put into the image? Great!

We will hook up your images with phablet-flash for you if you just follow the instructions below.

Prerequisites

  1. Follow our porting guide to produce an image for the device class you're working on.

  2. Set up a page under Touch/Devices/<vendor> using the Touch/Devices/PortTemplate page as a template.

  3. Fill it out as good as you can.
  4. Add it to our list of ports.

Storing the image meta-information

  1. Create a Launchpad team for the port maintainers. Use <vendor>-image-dev (ie. endeavoru-image-dev) as the name of the team.

  2. Make the phablet-ports-admins team, owner of your team. You can do that easily at https://launchpad.net/~<vendor>-image-dev/+reassign. We require this, so that we can easily add more port maintainers in case team members get inactive.

  3. Set up Bazaar with Launchpad. (Some will have done this already.)
    1. Register your SSH key in Launchpad: https://launchpad.net/~/+editsshkeys

    2. Run bzr launchpad-login <your LP ID>

  4. Create a bzr branch with all the necessary information.
    1. bzr init <vendor>

    2. cd <vendor>

    3. create manifest.json and put the URL of your image in there. The notation is in JSON formatand it has the following values:

      • Image URLs: You will need to provide URLs to images, which don't require any user interaction for downloading. Just pointing wget or curl at the URL should do the trick. (goo.im or ubuntuone.com for example.)

        • device (mandatory): it points to the image you're providing.

        • ubuntu (optional): the Ubuntu image, by default it's the latest official Ubuntu image.

      • hash (optional): hash sum of the current image.

      • hash_func (optional): either md5 or sha256.

      • revision (optional): provide a revision for the current image.

      Something like this could work:

      {
         "device": "http://goo.im/devs/MaxWallstedt/ubuntu-touch-i9100/current/saucy-preinstalled-armel-i9100.zip",
         "ubuntu": "http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/saucy-preinstalled-phablet-armhf.zip"
      }


      Save the file.

    4. vi license and put as much licensing information in there as possible. It's important that users know which blobs/firmware are available under which license.

    5. bzr add license manifest.json

    6. bzr commit -m "initial commit"

    7. bzr push lp:~<vendor>-image-dev/phablet-image-info/<vendor> (ie: lp:~endeavoru-image-dev/phablet-image-info/endeavoru)

  5. Ask the Phablet Port Admins to enable your device images in phablet-tools. Simply use this contact form: https://launchpad.net/~phablet-ports-admins/+contactuser

Touch/MakingPortsAvailable (last edited 2013-08-09 13:46:24 by dholbach)