question about bzr model of shared repository

[Alexander Belchenko]

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

I wonder why in case of shared repository branches always
should be created inside the shared repository?
Why bzr don't allow to create lightweight branches (vs lightweight
checkouts) with normal branch object in .bzr, normal working tree
object in .bzr, but with reference to shared repository?

What I missing here? Probably it's better (to me) to read about
main assumptions and limitations of bzr model, does such document exists?

I'm ask about lightweight branches because I often want to branch
lightweight checkout and get new lightweight checkout.
So each time I go to shared treeless repo, do branch,
then do lightweight checkout. It's boring.
'cbranch' command looks too complex for me.
I'm still don't understand policies, and in most cases
I think I don't need them. Moreover, when I move repo/branch
over filesystem I need to modify configuration file accordingly,
and it's boring me. I think Branch6 approach to keep all config
parameters inside .bzr/branch directory is right way.

[µ]


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGO2CjzYr338mxwCURAut0AJ4lUJtwDLqT9SWkevqVoJxoW1gFmQCeKxW0
iuHug1sNdtq8FK0CrAeQSCc=
=z0Tk
-----END PGP SIGNATURE-----