Out of dir BZR repository?

[Sabin Iacob]

Jorgen Bodde wrote:
> Hi all,
>
> This is my current situation. My boss only wants checkins on finished
> software into the main branch which is logical because the build
> system must keep on running. I want to keep a seperate BZR branch of
> my code so that I can keep versions. That BZR repository info should
> not be in my work dir, or else I have to tell SVN all the time that it
> is not something it should look at. Preferrably I would like the keep
> the BZR versioning on a network share so that it gets backed up
> periodically.
>
> So is it possible to store the ".bzr" dir somewhere else? I don't mind
> having to specify it everytime (I will use a batch file for that) and
> it gives me the benefit of having my own versioned info and SVN info
> seperated.
>
> Any other solutions to the situation I sketched are also welcome ;-)
>   

you can work directly with svn, using the bzr-svn plugin, so instead of 
svn commit you can do bzr commit on the same source tree (bzr treats svn 
working trees as lightweight checkouts, so if you do bzr diff/commit in 
a svn-controlled directory out of habit, it will work, albeit a lot 
slower); what I do is maintain a local bzr branch, hack away in (it 
handles like an usual bzr branch) and push to the svn trunk when needed

the only nuisance I encountered is that someone in the svn camp felt 
that it is a must for users to see the property changes regardless of 
whether they want it or not, hence there is no way to get the diff 
without them without actually parsing the output, so a post-commit mail 
with a 5-line diff will also include ~25KB of useless (wrt humans 
understanding what has changed) property changes.