At 2002/05/03 15:13 +0200, =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= wrote:
>Right. Hm. On the one hand, you'd want the format strings to be global to
>the repository. On the other hand, you want them versioned. The notion of
>"repository properties" comes to mind. They'd be versioned like node
>properties, but apply to the whole repository, and accessible through any
>node. Say in the "svn:repo:" namespace.
This goes back to multiple projects. You may want to have a format string
defined one way in one project an another way in another project (imagine,
for example that you do work for multiple clients, each with slight but
strict differences in how $Id$ should be formatted). You may want some
format strings defined for one project and not for another.
How about building a list of defined keywords and their formats by defining
them at the directory level and working your way up to the root looking for
definitions, with the lowest-level definition taking precedence? For example:
/stuff defines
$Id$ = "<author> <date yyyy.mm.dd>"
/stuff/client1 defines
$Id$ = "<author> <version> <date mm/dd/yy>"
$Copy$ = "(c)1998-<date yyyy> Client One Inc."
/stuff/client2 defines
$Id$ = "<author> <rootfile> <version>:<rev>"
$Copy$ = "(c)2002 Client Two Corp."
$Credits$ = "Brought to you by the cool guys at Cool Guys Inc."
So in this structure $Credits$ is only defined for files defined under the
client2 directory.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 3 15:48:47 2002