[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN Keyword substuition question

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Mon, 22 Sep 2008 13:36:34 -0500

On Sep 22, 2008, at 7:25 AM, Joe Wade wrote:

> Have a SVN useage question. Ultimately I am looking to perform a
> custom
> keyword substuition.

We just had this question actually:


It's not possible with Subversion for several reasons.

> But as I do not think that is currently supported
> (issue 890 seems like people are trying), I may need some help with a
> work around.
> I would like (or at least the powers that be would like) to append a
> license and copyright statement to the top of every source & header
> file. I don't really want to manually edit all the files for a few
> reasons. First, I don't want to have to maintain the files as the
> statements change (which they shouldn't but of course will). There
> are also quite a few files (big project), so I don't really want to
> go through all the files manually.
> I have investigated using svn:property(s) (as the book suggests)
> to embedd license and copyright information, but I really need them
> to be visible at the top of each of the files. The properties are
> only
> (correct me if I am wrong) through the svn prop* commands.
> I could create a sed script (or something) to put the statements at
> the top of the file, but I am hoping there is a nicer way for me
> to do this with SVN. I think the ultimate solution would be to have
> a $license$ and $copyright$ keyword on the files and have SVN
> do a substuition during checkout/checkin, but in the meantime I
> need to get this done. Any ideas? Can I get this functionality with
> the current set of hook scripts?

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-22 20:37:02 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.