Some plans for scmproj

[Alexander Belchenko]

Michael Gliwinski пишет:
> On Wednesday 09 December 2009 14:12:25 Alexander Belchenko wrote:
>>> One question I have here is, does this mean that a bzr working tree will
>>> have to be at the root of the project directory?  Or do you plan to
>>> work-around this somehow?
>> Yes, today you can have one branch in the root of project tree,
>> specifying in the project.cfg:
>>
>> [component "foo"]
>> RELPATH = .
>> ...
>>
>> But it was mandatory. Now this will be mandatory to have *some* bzr tree
>> at the root of the project. If you don't like this you may use your old
>> .scmproj control branch as top tree. This is up to you. Such tree can be
>> almost empty (only keep .bzrmeta/scmproj/config) and that's all.
> 
> 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.

>>> I'm not sure what you mean that it's harder to track things?
>> 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.

>>> My use case is more for maintaining a project composed of multiple
>>> components, so I find scmproj's ability to run e.g. status for all
>>> components very useful.  The only peculiarity here is that I can't have a
>>> branch in project root but still need to keep some links there, pointing
>>> to files within the actual component branches.
>> You can have a branch in project root. Why you think you can't? I'm not
>> quite understand your point.
> 
> 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?