WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
> On 2006-09-01 15:30:19 +1000, Charlie Allom wrote:
>> On Fri, Sep 01, 2006 at 01:51:24AM +0200, Vincent Lefevre wrote:
>>> Concerning the files under the dports directory, I'd say we should
>>> do that on the Portfiles (as it was the case under CVS), but not on
>>> the patches.
>> this isn't very nice..
>> turns out (afaict) to get $Id$ working, you will need to set these
>> under ~/.subversion/config:
>> enable-auto-props = yes
>> Portfile = svn:keywords Id
>> <..other things?..>
>> EVERY developer will need to set this to make it worthwhile!
>> unless I'm missing something with svn here, can someone else chime
> The developers don't need to use auto-props. They can also do the
> following to add a Portfile:
> svn add Portfile
> svn ps svn:keywords Id Portfile
> svn ci Portfile
> The auto-prop is just a rule so that the "svn ps ..." line is
> automatically performed when doing the "svn add ...".
> If they forget to add the Id keyword, they can still do it later, or
> some other developer can do it, or a script can fix it (just like a
> script updates the PortIndex file); the svn:keywords is versioned,
> like all non-revision properties.
If you want to force developers to attach this property to all
portfiles, you can write a pre-commit hook that rejects the commit of
any portfile that does not have those keywords set. The error message
you print can explain to the committer how to correct it (by using
svn ps or the auto-props in the config file).