View Single Post
Old 09-17-2011, 10:36 AM   #10
kacir
Wizard
kacir ought to be getting tired of karma fortunes by now.kacir ought to be getting tired of karma fortunes by now.kacir ought to be getting tired of karma fortunes by now.kacir ought to be getting tired of karma fortunes by now.kacir ought to be getting tired of karma fortunes by now.kacir ought to be getting tired of karma fortunes by now.kacir ought to be getting tired of karma fortunes by now.kacir ought to be getting tired of karma fortunes by now.kacir ought to be getting tired of karma fortunes by now.kacir ought to be getting tired of karma fortunes by now.kacir ought to be getting tired of karma fortunes by now.
 
kacir's Avatar
 
Posts: 3,450
Karma: 10484861
Join Date: May 2006
Device: PocketBook 360, before it was Sony Reader, cassiopeia A-20
Quote:
Originally Posted by kovidgoyal View Post
Commit will only commit your changes locally, unless you have used bzr bind to bind your branch to a remote one.
Thank you for clarification.

So. The steps that work for me on Linux are:
  1. Set your ID - bzr whoami John Smith <JSmith@thisisnotmyemail.com>
  2. Get sources from net to my machine - bzr branch lp:calibre (Issue command from inside your working directory, for example ~/src directory. The command will create ~/src/calibre directory and populate it (about 400 Mega Bytes of files) )
  3. Make desired small tweaks, such as replacement of splash screen, icons, little change in some *.py file
  4. Commit your changes - bzr commit (issue command in your private calibre development directory ~/src/calibre)
  5. Every week or so merge changes from the net, so your version of Calibre is still up-to-date - bzr merge (again issue command in your private calibre development directory)
  6. Repeat steps 3-5
kacir is offline   Reply With Quote