← Back to team overview

pkgme-devs team mailing list archive

Re: pkgme for extras

 

On Mon, 30 Jul 2012 11:01:04 +0100, Jonathan Lange wrote:
Hey Allison,

Thanks for the patch!

This sounds an awful lot like the backends we already have in place
for supporting submissions that come through developer.ubuntu.com,
lp:pkgme-devportal.

Ah, at UDS that didn't exist yet. Glad I checked in again before continuing. :) I'll redirect my efforts to refining what's there.

They look for a `devportal-metadata.json` file, that might look
something like this::

  {
      "package_name": "jabberwocky",
      "description": "The Jabberwocky, by Lewis Carroll",
      "icons": {
          "48x48": "jabberwocky.png"
          }
  }

And then consult that file for things that pkgme can't already figure out.

This is pretty much exactly what I was aiming for.

Does it still try to run setup.py to figure out Python packages? Or, does it extract useful snippets of text from the setup.py? Or, ignore setup.py entirely?

It does some kind of handling for license, but I'm not sure if that's
what you want for ARB.

If the output matches the Debian 1.0 format for debian/copyright, that's all we need.

What's driving the requirement for varying the source format?

Overall, I'd recommend starting with lp:pkgme-devportal and patching
it if it doesn't meet your needs. We probably want it to work for both
ARB & commercial apps.

Extras does have some unique output requirements such as:

- The version in debian/changelog has -extras12.04.1 appended to it.
- The package installs in /opt/extras.ubuntu.com/pkgname (last I checked you install in /opt/pkgname)
- They're generally native packages rather than tarball releases.
- For the most part we want very simple packaging, possibly turning off pkgme features.

It also needs to handle lenses and scopes (which can be detected from the existence of directories named "lens" and "scopes" in the top level of the tarball).

(And, I may be missing a few things, details at https://wiki.ubuntu.com/AppReviewBoard/Submissions/PackageQuickStart, which is the guide I want pkgme to replace.)

So, I'm not sure if it makes sense to have a separate extras backend (that reuses a lot of behavior from the devportal one), or to patch in some small alterations to the existing devportal backend. I'll take a look at the devportal branch.

Thanks!
Allison



Follow ups

References