Bzr

Differences between revisions 1 and 3 (spanning 2 versions)
Revision 1 as of 2013-03-19 14:43:52
Size: 1437
Editor: zequence
Comment:
Revision 3 as of 2013-03-19 14:55:14
Size: 1685
Editor: zequence
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
[[http://bazaar.canonical.com/en/|Bazaar]] is a GNU version control system, sponsored by Canonical used for keeping track of sources at [[https://code.launchpad.net|code.launchpad.net]]. Most, or all Ubuntu sources exist as bzr branches. [[http://bazaar.canonical.com/en/|Bazaar]] is a GNU version control system, sponsored by Canonical and used for keeping track of sources at [[https://code.launchpad.net|code.launchpad.net]]. Most, or all Ubuntu sources exist as bzr branches.
Line 12: Line 12:
Getthe source for a development release branch: There are some nice builtin functionalities in bzr. Getting Ubuntu source is one of them.
Line 14: Line 14:
||bzr branch ubuntu:<package>|| Get the source for a development release branch:

||<#f4f0cb>bzr branch ubuntu:<package>||
Line 18: Line 20:
||bzr branch ubuntu:jackd2|| ||<#f4f0cb>bzr branch ubuntu:jackd2||
Line 22: Line 24:
||bzr branch ubuntu:<release>/<package>|| ||<#f4f0cb>bzr branch ubuntu:<release>/<package>||
Line 26: Line 28:
||bzr branch ubuntu:precise/jackd2|| ||<#f4f0cb>bzr branch ubuntu:precise/jackd2||
Line 30: Line 32:
 /!\ Do not add several features committing them all at once. This makes it hard to oversee changes. A feature change may mean that you edit more than one file though. /!\ '''Do not add several features and then commit them all at once. This makes it hard to oversee changes. However, making a feature change often means that you edit more than one file. So, it is the feature that should be commited, not each changed file by itself.'''
Line 34: Line 36:
{{{
bzr add <yournewfile>
}}}
||<#f4f0cb>bzr add <yournewfile>||
Line 38: Line 38:
While you'll probably seldom do it this way (if you're working on a debian package), this is how to create a standard bzr commit: Though you'll seldom do it this way (since you're propably working on a debian package), this is how to create a standard bzr commit:
Line 40: Line 40:
{{{
bzr commit -m "a description of your commit"
}}}
||<#f4f0cb>bzr commit -m "a description of your commit"||
Line 46: Line 44:
{{{
debcommit
}}}
||<#f4f0cb>debcommit||

What is Bazaar?

Bazaar is a GNU version control system, sponsored by Canonical and used for keeping track of sources at code.launchpad.net. Most, or all Ubuntu sources exist as bzr branches.

bzr command cheat sheet

Get Ubuntu Source

There are some nice builtin functionalities in bzr. Getting Ubuntu source is one of them.

Get the source for a development release branch:

bzr branch ubuntu:<package>

For example:

bzr branch ubuntu:jackd2

Or, if you want the source for a specific release:

bzr branch ubuntu:<release>/<package>

For example:

bzr branch ubuntu:precise/jackd2

bzr commits

Warning /!\ Do not add several features and then commit them all at once. This makes it hard to oversee changes. However, making a feature change often means that you edit more than one file. So, it is the feature that should be commited, not each changed file by itself.

To make a commit, you would first make changes. To make new files commitable, you would first need to:

bzr add <yournewfile>

Though you'll seldom do it this way (since you're propably working on a debian package), this is how to create a standard bzr commit:

bzr commit -m "a description of your commit"

If you're working on a Debian package, you'll first edit debian/changelog, and then use debcommit. debcommit reads debian/changelog and uses the descriptions of changes from there.

debcommit

UbuntuStudio/Bzr (last edited 2013-05-17 01:32:45 by zequence)