Re: [Feature] unique version numbers

Greg Hudson wrote:
> If we store the value, then we only have to do extra work for files
> which use the offending keywords (GlobalRevision for update, URL and
> GlobalRevision for switch).

And we are storing exactly the same information in both the entries file
and the props/file.svn-work file (in different forms).

How about this as a compromise: store a new value in entries, say
'requires-keyword-expansion' and set that at an appropriate time that we
are already rewriting the entries file (say update) iff one of the
defined keywords is set on this file (currently URL and GlobalRevision).
  Then we have the best of both worlds: we only need to read the entries
files to know which files need updating and we use the existing keywords
expansion code to rewrite the file(s) without having to special case the
coding.

It should always be safe to completely re-expand any existing keywords
(since the values either changed or didn't change) and we are just
flagging those files where we *have* to change them. We might wind up
rewriting a file with an unchanged $URL$ but it is a much simpler
interface to program, since it just uses the current API.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org