John Peacock wrote:
>
> You misunderstand how keywords work in general. The client code only
> interprets a keyword at the point in time the file is changed (either
> through an update, checkout, or export). There is no code that walks
> through the WC and re-expands keywords based on some external event _if
> the file itself hasn't been changed_.
I absolutely understand _why_ it is the way it is
(mostly speed reasons)
but it means that one gets slightly different files,
dependent on the method used to checkout a WC.
at least 3 methods:
-) fresh checkout trunk at revision x
would contain "/trunk/foo"
-) fresh checkout a tag of that trunk revision x
would contain "/trunk/tag/foo"
-) checkout trunk and switch to that tag
would contain either "/trunk/tagxyz/foo"
or "/trunk/foo" depending on the WC's
prevous content.
If its critical to regenerate 100% identical files,
there is probably only one solution:
tag, delete_wc / fresh checkout tag, build, release it.
:-)
c.a.t.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 22 23:18:00 2004