Differences between revisions 3 and 4
Revision 3 as of 2011-07-18 09:53:54
Size: 2052
Editor: jml
Revision 4 as of 2011-07-18 09:55:10
Size: 2125
Editor: jml
Deletions are marked like this. Additions are marked like this.
Line 14: Line 14:
|| Steve George || Business development || 2011-07-04 ||
Line 16: Line 17:
== User stories == ## == User stories ==
Line 20: Line 21:
=== $STORY_NAME === ## === $STORY_NAME ===
Line 22: Line 23:
'''As a ''' $PERSON<<BR>>
'''I want ''' $FEATURE<<BR>>
'''so that ''' $BENEFIT<<BR>>
## '''As a ''' $PERSON<<BR>>
## '''I want ''' $FEATURE<<BR>>
## '''so that ''' $BENEFIT<<BR>>

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


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.




Last consulted

Rick Spencer

Ubuntu Engineering manager


Steve George

Business development



Constraints and Requirements


  • 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


  • 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


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)