the inventory must be updated as merge proceeds, not at the end

[Aaron Bentley]

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

John A Meinel wrote:
> Aaron Bentley wrote:
> 
> ...
> 
> 
>>Tree transforms should happen at a level above the filesystem level,
>>because what's on the disk may not match the WorkingTree.  Specifically,
>>we want to support CVS-style keywords.
>>http://bazaar.canonical.com/KeywordExpansion
> 
> 
> We do ??? 

Martin and Robert do, at least.

I really think CVS keywords are not the best answer to the
> problem. Educating people to a better way would be nice. Though we can
> always give in if too many people are stuck to it.

Education is often not the answer.  One thing I learned from tla was to
be suspicious of answering "I want foo" with "No, you don't, you want
bar".  Pretty much any UI wart was justified with "But working around
this problem will teach people how to use scripting better".

Some people like keywords and are willing to suffer CVS because bzr
doesn't have them.  We had one of those in IRC in the last week.

Also, it may not always be appropriate for the build system to depend on
the VCS.  For example, it may be useful to have expanded keywords in a
tarball.

> But you will still have the problem that the current state of the tree
> is X, but the file was only last modified in Y. 

It's conceivable that we could support both tree-revision(X) and
file-revision(Y) as keywords.  Did you notice the spec calls for
updating every keyword-expanded file every time the last-revision changes?

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

iD8DBQFDtBmB0F+nu1YWqI0RAoddAJ97kViDsYGqfa4O2ejmDNSU6QylRwCfZxeD
qfXiw45rQ0BBNdE/0awuB9c=
=sC8d
-----END PGP SIGNATURE-----