Interested in Participating

[Richard Wilbur]

On Tue, 2006-10-03 at 13:55 -0400, Aaron Bentley wrote:
> Richard Wilbur wrote:
> > it seems likely that one would want to install bzr as the new code is
> > not necessarily in the shell's path.
> 
> Could be, though it's an optional step.  I was assuming you already had
> another copy of bzr installed.  (I assume people would decide to contribute
> 
I had version 0.8 installed as that was the most recent available in
Synaptic for the Dapper repositories.  Since the latest development is
so much newer, I wiped out the old installed version and installed from
the downloaded development tree.  I am interested in the new
documentation for my development environment.  I also wanted to avoid
creating the development tree with any bugs or quirks apparent in
earlier versions.

> Actually, I use the downloaded copy as my bzr executable directly:
> 
> $ ln -s ~/bzr/bzr.dev/bzr ~/bin/bzr
> 

I'm curious:  why do you use the bzr/bzr.dev copy in place instead of
installing it?  Is it because there is no uninstall option for setup.py
and you want to run a recent release without a lot of hassle?

> I don't think installing bzr should be in the main flow of instructions,
> since a lot of people will already have it installed.  Maybe something
> like this:
> 
> - ---
> First, get a local copy of the development mainline
> ::
> 
>  $ mkdir ~/bzr
>  $ rsync -av bazaar-vcs.org::bazaar-ng/bzr/bzr.dev/ ~/bzr/bzr.dev
> 
> Optionally, you may install this copy of Bazaar.  See Installation_ for
> details.
> 
> Now make your own branch::
> - ---
> 
> Aaron

Sounds reasonable.

Thanks,

Richard