Help with plumbing a new WorkingTreeFormat in
John Arbash Meinel
john at arbash-meinel.com
Wed Jul 30 16:46:09 BST 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ian Clatworthy wrote:
| Rob,
|
| I've coded up a new WorkingTreeFormat that supports filtered views
| and now I need some direction on how to expose it and the upgrade
| logic. I've added some upgrade code to bzrdir.py to upgrade from
| WTF4 to WTF5 but I'm a bit lost after that. :-(
|
| In particular, can the format just "float" there without
| being the default? If so, how do I specify to upgrade to it?
| The upgrade command doesn't seem to support upgrading it directly.
| Do I need to create a new set of combinations of tree+branch_repo?
| Is there some code I can start from for writing the upgrade tests?
|
| My latest code is here:
sftp://ianc@people.ubuntu.com/home/ianc/public_html/bzr/bzr.views/.
| It's a loom and the format support is all in the layer above bzr.dev.
|
| Chat soon about this say? Phone is good but IRC might work better
| if others are interested in learning as well.
|
| Ian C.
|
|
I think you need to register a new bzrdir combination.
bzrlib.bzrdir.format_registry.register_metadir('views',
'bzrlib.repofmt.pack_repo.RepositoryFormatKnitPack5',
help='A WT format that supports views, and stackable branch...',
branch_format='bzrlib.branch.BzrBranchFormat7',
tree_format='python.path.to.my.WTFormat5',
)
Then you should have access to "bzr upgrade --format=views' (or bzr
upgrade --views).
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkiQjMEACgkQJdeBCYSNAAM4gQCdHry/kRj6HzUKdI8bLmj8/jKa
zugAn3pIxSil42VwJdxHN23+GTO7/zZC
=A2lr
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list