I spent a little bit of time mucking around with some Bazaar plugin ideas I've had.
The first is a command that switches from "branches and trees together inside a shared repository" to "treeless repository with lightweight checkouts". I ran it against a couple of my local repositories and it works out rather nicely. If you are thinking of using cbranch and the like, you should have a look at this plugin. If you don't know why it's a good idea, well, umm, maybe one of the other people on the Planet will blog an answer.
The second adds 'bzr new' to the command list.
$ bzr new awesomer
will create a new shared repository called 'awesomer' and a new branch in that repository called 'trunk'. If you think trunk is a terrible name, you can do:
$ bzr new awesomer devel
If you are like Tim or Aaron, you'll want your repository and branches separated from your working tree:
$ bzr --repository ~/repos/foo foo devel
I'd like to figure out a nice way of letting users specify a default directory for repositories to go into, for those people who always use the split model.
The plugin with both of these commands can be found at https://code.edge.launchpad.net/~jml/+junk/bzr-establish. As the "junk" in the name indicates, it's really rough code.
If either of these features sound like good ideas to you, let me know!
Saturday, October 4, 2008
Subscribe to:
Post Comments (Atom)
Twitter Updates
Blog Archive
-
►
2010
(68)
-
►
November
(14)
- testtools manuals
- Tests that print stuff
- Boiling kettles, unit tests and data
- Big or small?
- "Don't Make Me Think", thoughts for Launchpad
- Reviewing specs, rock on!
- Having an extra feature never hurts, rebutted
- And then what?
- Make it really easy to fix bugs on Ubuntu
- What else have you got?
- Ubuntu in a VM on OS X?
- Still going
- What to do, what to do
- Launchpad and UDS-N
-
►
November
(14)
2 comments:
The functionality in bzr new is great, but I very rarely start a project with a shared repo. Mostly, the branch comes first to see if the work in a branch is even worth it.
I was working on a similar idea of doing the shared repo and branch in one command thing. My idea was more about branching the trunk of another project into a shared repo. However, while I could get basic functionality, I got blocked on cases where the branch format is incompatible with the repo created, and found it difficult to check the existing branch's format, to make a compatible repo. I've tried a few approaches to no avail. :(
There basically aren't any branch formats that are incompatible with repository formats. You'd have to go back to formats that were current for bzr 0.7 to find such a thing.
Post a Comment