Bazaar has become a tool I’m using all the time. Using Bazaar as a version control system means using a command line interface. I haven’t found a feature-rich Bazaar GUI tool like the ones that exist for Subversion. I feel alright with using a command line interface for executing commands; but it is frustrating to edit text, review diffs, and manage merges in a command line environment. It just sucks! I want something better: a work-flow that keeps me productive, and an appropriate interface for the task at hand. Specifically, I want my version control system to be integrated with my Mac and the existing tools I use; I want to be able to:
- Manage my files and folders using Finder
- Write commit messages, view diffs, and manager merges in TextWrangler
Continue reading ‘Using Bazaar On a Mac’
Published on
February 22, 2009 in
Code.
Tags: bzr, VCS.
Bazaar is my prefered and default version control system. While searching for a replacement to Subversion it was clear that a distributed VCS was the way to go. This lead me to comparing Git, Mercurial, and Bazaar; ultimately choosing Bazaar for having a company backing it, great documentation, and easy transition from Subversion.
I tend to think that open source code I write falls into two categories: full projects, and everything else (examples, snippets, module). When the code I’m writing is turning into something I plan to release as an open source project, then I’ll release it on Google Code. For small chunks of code, especially code to supplement a post here, I’ve been releasing it to the files directory here.
Bazaar is built to work over standard protocols including HTTP; making it perfect to enhance a browsable directory on my server as a public ready-only Bazaar repository. This is precisely what I did with the /files directory; each sub-directory in /files is a bzr branch.
Feel free to bzr branch any branchs in my http://925html.com/files/ repository.
$ mkdir 925html
$ cd 925html/
$ bzr branch http://925html.com/files/branch_name