Some plans for scmproj

Michael Gliwinski Michael.Gliwinski at
Thu Dec 17 09:56:20 GMT 2009

On Monday 14 December 2009 21:24:38 Alexander Belchenko wrote:
> > Yes, that is what I meant actually.  I don't actually want to have a bzr
> > tree at the root of the project and I thought it would now become
> > mandatory to have some.
> I'm failing to understand why this is bad? Just for the record: native
> nested trees (TM) using the same approach btw.

This isn't bad per se, I'm only saying there are possible scenarios where I'd 
like to avoid that.  I.e. this probably relates to a small subset of scmproj 
use cases, I just happen to be working on a project which is among them.

> >> Commands like project-command, project-commit et al should be aware
> >> about existence of separate control branch. This is extra complexity for
> >> the code.
> >
> > Understood.  However I imagine some of this will still have to stay there
> > in order to be able to handle the scenario of project root separate from
> > location of control directory?  E.g. to be able to do something like:
> >
> >   $ cd ~/prj
> >   $ bzr project-commit --control=.scmproj
> >
> > to specify that the control tree is ~/prj/.scmproj
> I don't like this way to be honest.

I'm not a fan of that exact way neither.  I'm just thinking you'd need some 
way of specifying where the control branch is/should be located if not in 
project root (i.e. non-default behaviour).

A command-line option has the drawback that it would need to be specified to 
every command you run.  Maybe an env variable then?

> > I didn't actually mean that I can't have a bzr tree in project root
> > because the software doesn't allow it, but because the peculiarities of
> > my project don't allow it :)
> I don't understand this. Today you have to keep .scmproj directory in the
> root of the project. Tomorrow you'll need to have 2 directories there
> instead: .bzr + .bzmeta
> Why it so critical for you? Can you explain?

It isn't a show-stopper in a sense that everything would still work.  I'd 
really like to avoid that however because the project contains unversioned 
directory structures with various data, and because Bazaar searches for its 
control directory recursively up the tree, if someone runs a bzr command in 
wrong directory (you'd be surprised how often that happens, especially with 
ppl who do not feel "at home" at the command line) it will not do the right 

Michael Gliwinski
Henderson Group Information Services
9-11 Hightown Avenue, Newtownabby, BT36 4RT
Phone: 028 9034 3319

The information in this email is confidential and may be legally privileged.  It is intended solely for the addressee and access to the email by anyone else is unauthorised.
If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.
When addressed to our clients, any opinions or advice contained in this e-mail are subject to the terms and conditions expressed  in the governing client engagement leter or contract.
If you have received this email in error please notify support at

John Henderson (Holdings) Ltd
Registered office: 9 Hightown Avenue, Mallusk, County Antrim, Northern Ireland, BT36 4RT.
Registered in Northern Ireland
Registration Number NI010588
Vat No.: 814 6399 12

More information about the bazaar mailing list