Using Bzr

Using Bzr


Install bzr.

sudo apt-get install bzr

Make a Launchpad account, join the Runewin-team group

Link to team.

Download for the First time

bzr co lp:runewin

This creates a directory in where you are, named runewin, and puts all of the sourcecode inside that directory

Updating to the latest version

bzr update

Watch out if bzr complains about conflicts, if it does do

bzr conflicts

and it will tell you which files have conflicting code

Making changes

Make the edits or fixes that you intend to, then you'll need to Commit them


bzr commit

It will come up with a text box, along the bottom is a list of the files you are going to change

ALWAYS double check this, if anything is wrong, Ctrl-X and say NO to saving the file

If all seems well, You will need to supply a message to say What exactly you have changed. This must be done in this format:

- Something in Some file was Changed to …, from … . Give a Reason or reference a bug report in LP

While the message can be slightly more ambiguous, more detail is better.

Please do NOT commit a change until it has been tested as throughly as it can in your given circumstances.
Bugs will not be introduced if we are careful on this step

Adding New files

If you add new files, before attempting to commit them, you first need to mark them as a known file

bzr add *

This will mark every file in your directory as a known file

Then, commiting will still be needed to have that file pushed up into bzr

I'm not sure what changes I made, and I dont want to commit broken code!

This is a little more in-depth, so pay attention

bzr diff | less

It will show something like this :

=== modified file 'lastbuild'
--- lastbuild   2009-11-08 15:16:29 +0000
+++ lastbuild   2009-11-08 15:17:38 +0000
@@ -1,1 +1,1 @@

=== modified file 'runeinfo/test/'
--- runeinfo/test/   2009-05-05 16:14:45 +0000
+++ runeinfo/test/   2009-11-09 20:44:23 +0000
@@ -28,7 +28,6 @@
 button = gtk.Button("I can has big button?")
-print "K."

 # Do NOT go into a gtk.main() because runewin does that once all
 # applets are initialised.

Lines starting with === merely mention which file it is talking about
Lines starting +++ and —- tell you the date, time, etc about the file
The line starting @@ tells you which line (and how many) are bieng changed

Now, you'll see extracts of code, some above and some below code that you have edited in the file specified

lines starting with one + are code that you added to the file specified
lines starting with one - are code that you removed from the file specified

Use the keyboard Up/Down keys to scroll through the whole list of changes

If all goes well, You'll remember what the changes are, and can revert any that you don't care for anymore, and go ahead with the ones you want.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License