Documente Academic
Documente Profesional
Documente Cultură
Release 2.3.0dev1
Bazaar Developers
August 13, 2010
Contents
1 2 3 4 5 6 7 8 9 Introduction Installation Introducing yourself Putting les under version control Making changes to your les Viewing the revision log Publishing your branch with sftp Publishing your branch with Launchpad Creating your own copy of another branch i ii ii ii iii iii iv iv iv v v v
10 Updating your branch from the main branch 11 Merging your work into the parent branch 12 Learning more
1 Introduction
Bazaar is a distributed version control system that makes it easier for people to work together on software projects.
Over the next ve minutes, youll learn how to put your les under version control, how to record changes to them, examine your work, publish it and send your work for merger into a projects trunk. If youd prefer a more detailed introduction, take a look at Learning More.
2 Installation
This guide doesnt describe how to install Bazaar but its usually very easy. You can nd installation instructions at: GNU/Linux: Bazaar is probably in your GNU/Linux distribution already. Windows: installation instructions for Windows. Mac OS X: installation instructions for Mac OS X. For other platforms and to install from source code, see the Download and Installation pages.
3 Introducing yourself
Before you start working, it is good to tell Bazaar who you are. That way your work is properly identied in revision logs. Using your name and email address, instead of John Does, type:
$ bzr whoami "John Doe <john.doe@gmail.com>"
Bazaar will now create or modify a conguration le, including your name and email address. Now, check that your name and email address are correctly registered:
$ bzr whoami John Doe <john.doe@gmail.com>
Note for Windows users: use Windows Explorer to create your directories, then right-click in those directories and select New file to create your les. Now get Bazaar to initialize itself in your project directory:
$ bzr init
If it looks like nothing happened, dont worry. Bazaar has created a branch where it will store your les and their revision histories. The next step is to tell Bazaar which les you want to track. Running bzr add will recursively add everything in the project:
Next, take a snapshot of your les by committing them to your branch. Add a message to explain why you made the commit:
$ bzr commit -m "Initial import"
As Bazaar is a distributed version control system, it doesnt need to connect to a central server to make the commit. Instead, Bazaar stores your branch and all its commits inside the directory youre working with; look for the .bzr sub-directory.
Bazaar will create a myproject directory on the remote server and push your branch to it. Now anyone can create their own copy of your branch by typing:
$ bzr branch http://www.example.com/myproject
Note: to use sftp, you may need to install paramiko and pyCrypto. See http://bazaar-vcs.org/InstallationFaq for details.
Note: +junk means that this branch isnt associated with any particular project in Launchpad. Now, anyone can create their own copy of your branch by typing:
$ bzr branch lp:~john.doe/+junk/myproject
branch,
including
its
revision
history,
at
Bazaar will download all the les and complete revision history from the bzr-gtk projects trunk branch and create a copy called bzr-gtk.john. Now, you have your own copy of the branch and can commit changes with or without a net connection. You can share your branch at any time by publishing it and, if the bzr-gtk team want to use your work, Bazaar makes it easy for them to merge your branch back into their trunk branch.
If youre happy with the changes, you can commit them to your personal branch:
$ bzr commit -m "Merge from main branch" Committed revision 295.
You can now email the merge directive to the bzr-gtk project who, if they choose, can use it merge your work back into the parent branch.
12 Learning more
You can nd out more about Bazaar in the Bazaar User Guide. To learn about Bazaar on the command-line:
$ bzr help