Quote:
Originally Posted by Agama
How often is it a good idea to update and how do I do it? (or is this a "How long is a piece of string" question?). Does it require another full download? (This took nearly 2 hours first time round).
|
I update before looking at code or changing anything, often more than once per day. Reasons:
- I don't want to be confused by something that behaves differently from what the code says it should do.
- I want to see bug fixes.
- Looking at changes, and especially the refactoring changes, is a good way to learn.
- I don't want to change code that is no longer in calibre.
I always update before submitting code to be sure that I am not submitting something that won't work or that conflicts with some other change. Of course, if you are not doing development on calibre's trunk (as I do) and are not depending on the code you are looking at being correct (as I am), then there is no requirement to upgrade. In the end, the decision is yours.
As for how to upgrade, running "bzr pull" from inside the source tree will get all the changes from the last time you did a pull/download. This will work only if you have not made any changes to a file under version control. If you have made changes, then you can toss the changes into the trash can using "bzr revert". You might (or might not) want to use the --no-backup option. If you have made changes you want to keep, then things are more complicated.
In your case, the first "pull" will take a while because it must download so many versions, but it will take less time than a full download. I find that daily pulls run in seconds. The exception is Friday after a release when all the translations are downloaded, in which case it can sometimes take nearly a minute but usually run in around 30 seconds. I have a very fast internet connection (100 Mbit), so your mileage could easily be worse than mine.