Bazaar as Subversion replacement

[Martin Pool]

On 16 Jan 2007, Nicholas Allen <allen at ableton.com> wrote:
> 
> >This is pretty complicated to do properly.
> >
> >A stopgap would be to have a precommit hook that fixed the line endings
> >whenever you committed.  Would that kind of solution be acceptable?
> >  
> Currently this is easy in svn and I think there would be too much chance 
> that a developer doesn't set this up properly. Wouldn't each developer 
> need to do this themselves? So actually I doubt this would be a viable 
> solution. I think the VCS needs to support this feature as easily as 
> possible because cross platform development is a very common situation. 
> Unless it is as easy as Subversion's implementation there is no way we 
> could migrate without this. It is the number one show stopper for us.

Well, that's pretty useful feedback, so thankyou.  Is the situation in
svn just perfect for your situation or is there anything else we should
take into account?

Lineending conversion is divisive: some people have got into trouble
using it, but to others it's necessary.

The basic approach of svn, in our terms, is that a filter is interposed
between the on-disk files when they're read or written.  This would not
be so hard to add.

> >>2 No support for tags.
> >>    
> >
> >That doesn't seem like a fair complaint, given that SVN doesn't support
> >tags, either.  Martin is working on proper tags, but you can always do
> >it the way SVN does.
> >
> The difference is that svn stores all tags in the same repository. I 
> guess you could use a shared repository and then branch into a Tags 
> directory like SVN does. It probably shouldn't be so high on our 
> priority list as we could even maintain a text file that contained 
> mappings from tag names to revids so this is not a complete show stopper 
> for us. I am also happy to hear that bzr has some implementations for 
> the tags feature too.

It's a high priority for me to land this for the next release.  There
should be a patch for review, including the documentation, some time
soon.

-- 
Martin