Re: CVS $Log$ equivalent in Subversion?

Bob Bradley wrote:
>
> Is there any chance an equivalent to $Log$ might be implemented in
> Subversion in the future?

Short answer - not likely. The use of $Log$ has long been a painful source of
difficulty.

Slightly longer answer; insert into your release script the equivalent of:

        svn log http://server/path/to/project > Changes

(or History or whatever). This file should NOT be versioned, but rather should
be generated afresh whenever you perform a release. For Perl modules which use
ExtUtils::Makemaker, the following example does just that:

> WriteMakefile(
> 'NAME' => 'version',
> 'VERSION_FROM' => 'lib/version.pm', # finds $VERSION
> 'PREREQ_PM' => {Test::More => 0.45}, # e.g., Module::Name => 1.1
> 'LIBS' => [''], # e.g., '-lm'
> 'DEFINE' => '', # e.g., '-DHAVE_SOMETHING'
> # Insert -I. if you add *.h files later:
> 'INC' => '', # e.g., '-I/usr/include/other'
> # Un-comment this if you add C files to link with later:
> 'OBJECT' => '$(O_FILES)', # link all the C files too
> dist => {
> PREOP => 'svn log > ${DISTVNAME}/Changes',
> },
> );

(this is from an actual module which I maintain).

HTH

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org