launchpad help|
Size: 5567
Comment:
|
Size: 5176
Comment: work in progress
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 40: | Line 40: |
| Don't worry about the login notice, as we're not yet uploading anything to Launchpad | '''Note:''' Don't worry about the login notice, as you're not yet uploading anything to Launchpad. |
| Line 44: | Line 44: |
| == Other branches == | You can use this hassle-free way of obtaining branches for any project that has code registered in Launchpad. All you need is the Launchpad name of the project, which you can find by looking at the final portion of the URL to the project's Launchpad overview page. For example: in GnomeDo's case that's ```https://launchpad.net/do``` |
| Line 46: | Line 46: |
| Let's visit [[[[https://code.launchpad.net/do|GnomeDo]]|GnomeDo's code overview page]. Here you can see a list of the GnomeDo-related branches that Launchpad knows about. | == Other branches associated with a project == If you want to download something other than a project's main line of development, you need to visit the project's code overview page. Let's visit [[[[https://code.launchpad.net/do|GnomeDo]]|GnomeDo's code overview page]. Here you can see a list of all the GnomeDo-related branches that Launchpad knows about. |
| Line 51: | Line 55: |
| Launchpad lists the branches in order of likely importance. So, the branch that the GnomeDo team have marked as their current development focus comes first - and is what you get when you use ```bzr branch lp:do```. At the time of writing, the following two branches are associated with GnomeDo's ''0.6'' and ''devel'' branches. The address you need to give Bazaar is also shown for both of these branches: ```do/0.6``` and ```do/devel```. | Launchpad lists the branches in order of likely importance. So, the branch that the GnomeDo team have marked as their current development focus comes first - and is what you get when you use ```bzr branch lp:do```. At the time of writing, the following two branches are also associated with GnomeDo series; in this case ''0.6'' and ''devel''. The address you need to give Bazaar is also shown for both of these branches: for example, ```bzr branch lp:do/0.6``` and ```bzr branch lp:do/devel```. |
| Line 53: | Line 57: |
| === Non-official branches === | |
| Line 54: | Line 59: |
| Launchpad and Bazaar's flexibility mean that anyone can upload their branch of code and associate it with any project in Launchpad. This is great news because you can get near instant access to all development effort for that project. | |
| Line 55: | Line 61: |
| Click on any of the branches in GnomeDo's list and you'll see exactly what you need to type in order to download it and create your own local branch, using Bazaar. | |
| Line 56: | Line 63: |
| ||<tablestyle="float:right; font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 0 0;" style="padding:0.5em;">{{attachment:ian-mc.png}}|| ||<style="text-align: center;">'''An experimental branch of GnomeDo'''|| |
|
| Line 57: | Line 66: |
| Here, you can see every branch of code associated with GnomeDo that Launchpad knows about. | == Code hosted elsewhere == |
| Line 59: | Line 68: |
| == More than one branch for each project == | So far, we've looked at branches of code that are hosted directly on Launchpad. Hosting on Launchpad is a quick and free way to publish your branch. However, as we saw in the introduction, you can use Launchpad to get hold of code that's hosted elsewhere too. |
| Line 61: | Line 70: |
| Most projects have more than one line of development, such as | [[https://launchpad.net/bitlbee|Bitlbee]] is a gateway between various IM networks and IRC. The bitlbee trunk branch is hosted by Bitlebee themselves and mirrored by Launchpad. That makes no difference to actually getting hold of that branch. Simply type: |
| Line 63: | Line 72: |
| Use the first two paragraphs to summarise all the important points about this article. | {{{ $ bzr branch lp:bitlbee }}} |
| Line 65: | Line 76: |
| 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. |
Similarly, |
DRAFT: this page is a work in progress. Please seek further help or check the wiki index for a complete page on this topic.
Overview
Launchpad and Bazaar give you access to thousands of branches of code. With just a few keystrokes, you can download the code from any of the projects that has code registered in Launchpad.
|
Launchpad Code stats |
So, what does it mean to have code registered in Launchpad? Well, it can be one of four things:
- code in a Bazaar branch that's hosted directly by Launchpad
- a Bazaar branch that's hosted elsewhere and mirrored by Launchpad
- a Bazaar branch that's hosted elsewhere and monitored by Launchpad
- a Subversion or CVS repository that's imported into a Bazaar branch hosted by Launchpad.
If all you want is to get hold of that code, you don't need to worry about its exact relationship with Launchpad because Launchpad sorts all that out for you.
Getting code
GnomeDo is an application launcher for Gnome desktops. You can create your own branch of GnomeDo's trunk line of development with just a few keystrokes and without even having to visit Launchpad's web interface.
Once you've got Bazaar on your system, open a terminal and type the following:
$ bzr branch lp:do
Bazaar will now download the latest version of GnomeDo's trunk branch to your machine.
$ bzr branch lp:do You have not informed bzr of your launchpad login. If you are attempting a write operation and it fails, run "bzr launchpad-login YOUR_ID" and try again. Branched 524 revision(s).
Note: Don't worry about the login notice, as you're not yet uploading anything to Launchpad.
Now you have your own local branch of the GnomeDo trunk, complete with full version control. You can commit any changes you like to that branch and, when you're ready, upload your version back to Launchpad to sit alongside the trunk and any other GnomeDo branches.
You can use this hassle-free way of obtaining branches for any project that has code registered in Launchpad. All you need is the Launchpad name of the project, which you can find by looking at the final portion of the URL to the project's Launchpad overview page. For example: in GnomeDo's case that's https://launchpad.net/do
Other branches associated with a project
If you want to download something other than a project's main line of development, you need to visit the project's code overview page.
Let's visit GnomeDo|GnomeDo's code overview page]. Here you can see a list of all the GnomeDo-related branches that Launchpad knows about.
|
Branches associated with GnomeDo series |
Launchpad lists the branches in order of likely importance. So, the branch that the GnomeDo team have marked as their current development focus comes first - and is what you get when you use bzr branch lp:do. At the time of writing, the following two branches are also associated with GnomeDo series; in this case 0.6 and devel. The address you need to give Bazaar is also shown for both of these branches: for example, bzr branch lp:do/0.6 and bzr branch lp:do/devel.
Non-official branches
Launchpad and Bazaar's flexibility mean that anyone can upload their branch of code and associate it with any project in Launchpad. This is great news because you can get near instant access to all development effort for that project.
Click on any of the branches in GnomeDo's list and you'll see exactly what you need to type in order to download it and create your own local branch, using Bazaar.
|
An experimental branch of GnomeDo |
Code hosted elsewhere
So far, we've looked at branches of code that are hosted directly on Launchpad. Hosting on Launchpad is a quick and free way to publish your branch. However, as we saw in the introduction, you can use Launchpad to get hold of code that's hosted elsewhere too.
Bitlbee is a gateway between various IM networks and IRC. The bitlbee trunk branch is hosted by Bitlebee themselves and mirrored by Launchpad. That makes no difference to actually getting hold of that branch. Simply type:
$ bzr branch lp:bitlbee
Similarly,
