AutomagicBinaryPackaging

Differences between revisions 1 and 3 (spanning 2 versions)
Revision 1 as of 2011-07-11 13:14:07
Size: 1701
Editor: jml
Comment:
Revision 3 as of 2011-07-18 09:53:54
Size: 2052
Editor: jml
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
'''On Launchpad:''' ## Link to a blueprint, milestone or (best) a bug tag search across launchpad-project '''On Launchpad:''' [[https://bugs.launchpad.net/pkgme/+bugs?field.tag=binary|binary]]
Line 32: Line 32:
## What MUST the new behaviour provide?  * Take a binary tarball and turn it into a working source package
 * Upload the finished source package to a PPA
Line 36: Line 37:
## What would be nice to have, but is not essential  * Figure out version from the containing directory in the uploaded tarball, if necessary
Line 44: Line 45:
## Things that people might think are in scope, but are actually not.
Line 46: Line 46:
== Subfeatures == === Assumptions ===
Line 48: Line 48:
## Other specs that form a part of this one.
 * Given a binary tarball and information from the developer portal
 * Binary is built using C or C++
 
Line 52: Line 53:
## How will we measure how well we have done? Ability to re-package existing binary applications in the SoftwareCenter. Testing against:
 * The Clockwork Man 2
 * Uplink
 * World of Goo
 * bukkon
Line 57: Line 62:

There are three separate phases to this:
 1. Create a valid source package
 1. Upload that to Launchpad
 1. Integrate with the existing developer portal

Given binary tarballs from upstream software vendors, turn those into packages in a PPA as quickly and smoothly as possible.

Contact: JonathanLange
On Launchpad: binary

Rationale

Ubuntu has a SoftwareCenter where people can buy applications. We want to make it very, very easy for application developers to publish their apps in the software center. For many such folk, this means publishing binary applications.

Stakeholders

Name

Interest

Last consulted

Rick Spencer

Ubuntu Engineering manager

2011-07-11

???

User stories

$STORY_NAME

As a $PERSON
I want $FEATURE
so that $BENEFIT

Constraints and Requirements

Must

  • Take a binary tarball and turn it into a working source package
  • Upload the finished source package to a PPA

Nice to have

  • Figure out version from the containing directory in the uploaded tarball, if necessary

Must not

Out of scope

Assumptions

  • Given a binary tarball and information from the developer portal
  • Binary is built using C or C++

Measures of success

Ability to re-package existing binary applications in the SoftwareCenter. Testing against:

  • The Clockwork Man 2
  • Uplink
  • World of Goo
  • bukkon

Thoughts?

There are three separate phases to this:

  1. Create a valid source package
  2. Upload that to Launchpad
  3. Integrate with the existing developer portal

AutomagicBinaryPackaging (last edited 2012-03-08 11:44:11 by jml)