Two questions about init and init-repo

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Adeodato Simó wrote:
> * Aaron Bentley [Sun, 02 Jul 2006 16:11:00 -0400]:
> 
>> Since repositories would be just directories with branches in them, you
>> wouldn't want to init-repo an existing directory, including '.'.
> 
> Ok, I see the reasoning behind me. It seems, however, that I have the
> `mkdir foo; cd foo; $rcs init` sequence too hardwired that the above
> bites me each time I create a repository. But we don't know if the
> number of people with this issue is enough to win the above reasoning
> over.

I don't think it's a bad idea to change it.  The name does suggest that
it behaves like init, and it's not hard to make it do that.

>>> 2. Has there been talk about an option for init (maybe branch too?, hm)
>>>    to prevent the shared (with --trees) repository from being used?
> 
>> No, I don't think we've discussed that.  Obviously, there are
>> workarounds to achieve that, but how do you see it being useful?
> 
> Hm. I can only speak about my particular circumstance: a repo with trees
> with various branches of Tailor, and in some directory under them, a
> test area in which, cough, bzr branches get created and thrown away
> after each set of changes. I'm putting the tests elsewhere now that I've
> noticed how fast .bzr was growing.

One thing that you can do is put a standalone branch in the root
directory of your test area.  That will prevent any branches you create
there from using the shared repo.  It should be more convenient than
supplying an option every time you create a test branch, but it's not a
very intuitive solution.

I suppose you could use --format weave, since that format didn't support
shared repositories.

I guess if people want a --standalone option, it's probably best to
provide it.  It's just that each option we add makes bzr more intimidating.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEqDae0F+nu1YWqI0RAoAJAJ4vxRXiV8H0oJUrKuhekkimDT/1ZwCePR9x
21lVqMRbU3KCBaM4VFh8L8k=
=9a2Z
-----END PGP SIGNATURE-----