bazaar branch fails

[Martin Pool]

On Wed, Apr 30, 2008 at 11:37 AM, Rahul Nabar <rpnabar at gmail.com> wrote:
> On Tue, Apr 29, 2008 at 5:52 PM, Martin Pool <mbp at canonical.com> wrote:
>  >  If you mean hack Bazaar in the sense of modifying Bazaar itself to
>  >  support this - it might be possible, people have talked about this a
>  >  little before, but it would take some more discussion to work out the
>  >  right way to do it.
>
>  Thanks Martin. I doubt my skills are at a level where I could touch
>  the source. I was thinking in terms of options / wrapper etc. (or like
>  the symlinking workaround you actually suggested) BTW, was this left
>  out due to performance reasons? Or just a esoteric feature that nobody
>  relay wished for? Just wondering if I wait for the next version if
>  there is a decent chance of seeing it come in.

I don't think it's particularly performance related.  It's more that
while it's not ultra esoteric, it is not at the top of the list of
features particularly wished for.  So I don't see it being in any of
the releases in the forseeable future, but you can never tell when
someone, perhaps some new developer, will get motivated to add a new
feature.

>  >  As far as how to use Bazaar to do this now: I'd suggest making branch
>  >  directories for each individually-versioned file or set of files, then
>  >  symlinking them into another directory.
>
>  I think that's my best bet for now. But I'm not sure I actually
>  understand that workaround.....Let's say I have a ~/dirfoo/ with
>  script1 and script2. My .bzr directory is present in ~ where I did my
>  one and only bzr init.
>
>  Now I need to work on script1.devel1 and script1.devel2 (two
>  alternative ideas for a modification to script1) for a while and then
>  when satisfied merge and then test and finally convert into the
>  production version of script1. All the while I'm the only developer so
>  not really multi-user.

It might help if you say a bit more about what the scripts are for and
what kind of changes you're making.

Generally I would suggest that you make

 bzr init-repo ~/projectname
 bzr init ~/projectname/idea1
 bzr init ~/projectname/idea2
 ln -s ~/projectname/idea1/script1 ~/bin/
 vi ~/projectname/idea1/script1

If you see what I mean...

-- 
Martin <http://launchpad.net/~mbp/>