Christoph Bartoschek wrote:
> Am Donnerstag, 3. April 2008 schrieb John Peacock:
>> Christoph Bartoschek wrote:
>>> I cannot use the solution presented in the FAQ. Did subversion gain
>>> support for a sane solution? I've seen proposals to add a svn:template
>>> keyword. Is such a thing implemented?
>> Nothing has changed (which is why the FAQ answer exists). This is
>> really a client-side issue that is surprisingly subtle to resolve in a
>> secure fashion. It is better to implement the solution given in the FAQ
>> you cited into your build tool (if required file doesn't exist, copy the
>> template file and error out with a message to perform the local update).
>
> We have no control over the build tool. Additonally my use case does not
> involve template files. I've changed files and links of the official project
> to be able to compile it on my notebook. This changes should not be commited
> to because they would break everything for other users.
>
> One reason why the official project will not change its policy is that the
> current approach is already configurable. In the AFS filesystem links with
> the target @sys can be used for system specific configurations. Unfortunately
> NFS and most Linux filesystem do not support this. Here one has to change the
> links for each system.
>
> Greetings
> Christoph
No, subversion has not implemented this. I do not believe the devs have
it very high on their todo list considering the easy solution that
exists. If that solution doesn't work, then use the other one: a
pre-commit hook that denies all commits that try to change specified
files. IIRC, a .py exists in contrib/ that does that.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-04 00:13:57 CEST