Diff for "Packaging/PPA"

Not logged in - Log In / Register

Differences between revisions 61 and 62
Revision 61 as of 2017-01-06 15:34:56
Size: 4123
Editor: bryanquigley
Comment: Commercial PPAs are not in beta anymore
Revision 62 as of 2017-10-17 21:51:51
Size: 4408
Editor: cjwatson
Comment: update architectures documentation
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
When Launchpad builds a source package in a PPA, it creates binaries for: When Launchpad builds a source package in a PPA, by default it creates binaries for:
Line 30: Line 30:
You may request [[https://dev.launchpad.net/CommunityARMBuilds|ARM builds]] for PPAs that meet the listed conditions. At the moment, these will build on an AMD64 system using `qemu-user-static` to execute ARM binaries under emulation. Some builds (particularly those that make heavy use of threads) will not yet work this way. You may also request builds for arm64, armhf, and/or ppc64el. Use the "Change details" page for the PPA to enable the architectures you want.
Line 32: Line 32:
We use an Open``Stack cloud for security during the build process, ensuring that each build has a clean build environment and different developers cannot impact on one another's builds accidentally. At the moment, this cloud only has AMD64 compute nodes, limiting the set of architectures it can support. We hope to extend this to other architectures in the future, which will eliminate the need for `qemu-user-static`. Changing the set of architectures for which a PPA builds does not create new builds for source packages that are already published in that PPA; it only affects which builds will be created for new uploads. If you need to create builds for newly-enabled architectures without reuploading, go to "View package details" and then "Copy packages", select all the packages for which you want to create builds, select "This PPA", "The same series", and "Copy existing binaries", and submit the form using the "Copy Packages" button.

We use Open``Stack clouds for security during the build process, ensuring that each build has a clean build environment and different developers cannot affect one another's builds accidentally. These clouds do not yet have support for the powerpc and s390x architectures; when they do, it will also be possible to request those architectures in PPAs.

Launchpad Help > Packaging > Personal Package Archives

Overview

Using a Personal Package Archive (PPA), you can distribute software and updates directly to Ubuntu users. Create your source package, upload it and Launchpad will build binaries and then host them in your own apt repository.

That means Ubuntu users can install your packages in just the same way they install standard Ubuntu packages and they'll automatically receive updates as and when you make them.

Every individual and team in Launchpad can have one or more PPAs, each with its own URL.

Packages you publish in your PPA will remain there until you remove them, they're superseded by another package that you upload or the version of Ubuntu against which they're built becomes obsolete.

Note: CommercialHosting allow you to have private PPAs.

Size and transfer limits

Each PPA gets 2 GiB of disk space. If you need more space for a particular PPA, ask us.

While we don't enforce a strict limit on data transfer, we will get in touch with you if your data transfer looks unusually high.

Supported architectures

When Launchpad builds a source package in a PPA, by default it creates binaries for:

You may also request builds for arm64, armhf, and/or ppc64el. Use the "Change details" page for the PPA to enable the architectures you want.

Changing the set of architectures for which a PPA builds does not create new builds for source packages that are already published in that PPA; it only affects which builds will be created for new uploads. If you need to create builds for newly-enabled architectures without reuploading, go to "View package details" and then "Copy packages", select all the packages for which you want to create builds, select "This PPA", "The same series", and "Copy existing binaries", and submit the form using the "Copy Packages" button.

We use OpenStack clouds for security during the build process, ensuring that each build has a clean build environment and different developers cannot affect one another's builds accidentally. These clouds do not yet have support for the powerpc and s390x architectures; when they do, it will also be possible to request those architectures in PPAs.

Supported series

When building a source package you can specify one of the supported series in your changelog file which are listed at the Launchpad PPA page.

If you specify a different series the build will fail.

Activating a PPA

Before you can start using a PPA, whether it's your own or it belongs to a team, you need to activate it on your profile page or the team's overview page. If you already have one or more PPAs, this is also where you'll be able to create additional archives.

Your PPA's key

Launchpad generates a unique key for each PPA and uses it to sign any packages built in that PPA.

This means that people downloading/installing packages from your PPA can verify their source. After you've activated your PPA, uploading its first package causes Launchpad to start generating your key, which can take up to a couple of hours to complete.

Your key, and instructions for adding it to Ubuntu, are shown on the PPA's overview page.

Deleting a PPA

When you no longer need your PPA, you can delete it. This deletes all of the PPA's packages, and removes the repository from ppa.launchpad.net. You'll have to wait up to an hour before you can recreate a PPA with the same name.

Next steps

You can familiarise yourself with how PPAs work by installing a package from an existing PPA. You can also jump straight into uploading your source packages.

< Translation groups

Installing software from a PPA >

Packaging/PPA (last edited 2017-10-17 21:51:51 by cjwatson)