Diff for "PPA"

Not logged in - Log In / Register
Differences between revisions 1 and 16 (spanning 15 versions)
⇤ ← Revision 1 as of 2008-07-02 21:18:47 →
Size: 5522
Editor: 92-237-59-186
Comment:
← Revision 16 as of 2008-09-02 11:29:17 → ⇥
Size: 25
Editor: 92-237-59-186
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
'''DRAFT: this page is a work in progress. Please [[Feedback|seek further help]] or check the [[TitleIndex|wiki index]] for a complete page on this topic.'''

||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||

= Overview =

Ever individual and team registered in Launchpad gets their own apt repository. They're called Personal Package Archives; you'll probably see that shortened to PPA in most places.

Your PPA is an efficient and convenient way to distribute software to Ubuntu users. All you have to do is upload a source package and Launchpad will:

 * build binaries for x86, AMD64 and lpia architectures
 * host the binaries in your own apt repository
 * push updates to your users when you build new binaries.
 
Installing and uninstalling software from a PPA is just as easy for Ubuntu users as installing software from their operating system's primary archives. This makes it an ideal way to distribute beta versions, daily builds and other versions of your software for testing, without having to ask your testers to compile your software from source.

Personal and team PPAs work exactly the same, except that in the case of team PPAs then entire team has permission to upload to the archive.

= Installing software from a PPA =

PPAs work just like normal Ubuntu archives. You can install software in the usual way - for example, through ```apt-get``` or ```synaptic``` - and whenever there's an update Ubuntu will prompt you to install it.

/!\ '''Important:''' when you install software from a PPA, Ubuntu will warn you that it is unsigned. For more on why packages in PPAs aren't signed, [[PPA/FAQs#unsigned|see the PPA FAQs]].

== Adding a PPA to your Ubuntu repositories ==

To install packages from a PPA, you need to tell Ubuntu where to find it. You do this by giving Ubuntu the PPA's URL, which you can find on the PPA's Launchpad page.

Let's take a look at the [[https://launchpad.net/~awn-testing/+archive|AWN Testing team's PPA]] as an example. If you're using the most recent '''development''' version of Ubuntu, all you need do is copy these lines in the ```apt sources.list entries``` section of the page. For example:

{{{
deb http://ppa.launchpad.net/awn-testing/ubuntu intrepid main
deb-src http://ppa.launchpad.net/awn-testing/ubuntu intrepid main
}}}

If, like most people, you're using another version of Ubuntu - such as the most recent stable version - then you need to select it from the drop-down box. That'll automatically update the URLs you need to copy.

Take a look at the [[https://help.ubuntu.com/8.04/add-applications/C/extra-repositories-adding.html|Ubuntu guide to adding extra software repositories]] to find out how to add those URLs to your local Ubuntu system.

= Building your source package =

Before you start using your PPA to distribute software, you need to be familiar with building .deb source packages.
 

 and host them in your own apt repository.




 When upload an updated version of your package, your users' operating systems will prompt them to upgrade.


handles the rest, including:

 * building binaries for x86, AMD64 and lpia
 *
 
 
 
 

Using your Personal Package Archive (PPA), you can build and distribute software packages for use in Ubuntu and Debian.

 * build packages for x86, AMD64 and lpia architectures
 * automatically push updates to users
 *



Use the first two paragraphs to summarise all the important points about this article.

Tell the reader if this is the information they need as soon as possible.

= Instructional text =

Where appropriate, use step by step instructions:

'''Step 1:''' Give concise and unambiguous instructions.

'''Step 2:''' Try not to state the obvious, unless you're writing for a novice user.

{i} '''Note:''' Highlight important information with a note.

'''Step 3:''' Use a well cropped screen shot if it will help orient the reader. Don't let the screen shot replace instructional text: not everyone can see your screen shot. Don't worry about borders or annotation for small, cropped screen shots such as this.

{{attachment:screen-shot.png}}

{i} '''Warning:''' If you're about to tell the reader to delete or otherwise change something that would be hard to restore, warn them.


== Full screen shots ==

||<tablestyle="float:right; font-size: 0.8em; width:30%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">{{attachment:proj-announce.png}}||
||<style="text-align: center;">'''Describe the screen shot here'''||

Some screen shots will be better placed to the right of your text. As they're not placed directly below the text that they support, use a border and short description.

Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aliquam sagittis. Aliquam eros dui, scelerisque id, consequat in, accumsan vitae, pede. Suspendisse neque ligula, scelerisque ac, mattis ut, aliquam quis, odio.

Proin nunc nisi, fringilla ac, congue ac, luctus eu, lacus. Maecenas ac purus. Cras felis metus, ultricies non, euismod ac, accumsan eleifend, leo. Quisque imperdiet tempus tellus.

Ut euismod, diam nec adipiscing interdum, tortor orci fringilla nisi, vel blandit erat magna at nisi. Fusce hendrerit odio non metus. Mauris nisl massa, dapibus id, feugiat quis, blandit a, quam. Integer tincidunt feugiat nunc. Curabitur iaculis egestas elit. Nam imperdiet suscipit odio.		 #redirect Packaging/PPA

PPA (last edited 2008-09-02 11:29:17 by 92-237-59-186)