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

Re: Support for: Setting property on non-local target

From: Matthias Wächter <matthias.waechter_at_tttech.com>
Date: 2006-02-28 19:21:38 CET

Ben Collins-Sussman schrieb:
> On 2/28/06, C. Michael Pilato <cmpilato@collab.net> wrote:
>> Matthias Wächter wrote:
>>> What is it that blocks this feature from appearing? Is it just
>>> programming effort on the client side, or is it a lack of communication
>>> support between client and server? Or something else?
> Our reason has always been: official subversion clients cannot change
> versioned data unless it's done in a working copy first. It's the
> reason that we have screaming warnings all over the 'svnput.c' example
> code, and it's the same reason we don't allow writing versioned
> properties directly to the repository. You might clobber changes that
> you've never seen.

Do I understand you correctly that enabling this feature is another
"Very Bad Thing" that you (as a developer) don't want to be blamed for
implementing and releasing to the bad world?

I'm not getting the point anyway. If I screw up anything in my own
repos, it's my fault. We already have a hook script that must be present
to enable sensitive features like commit metadata (revprops) changes.
Why not add a hook for this as well so that someone who knows what he
does, can allow the clients to perform the action, anyone else does not?
Additionally, leaving a "Very Bad Thing" as a client-side-disabled
feature seems not very reasonable to me. Maybe this cannot be checked on
the server side, but that's another topic.

If I have hook scripts for commits installed, I always will get a
notification email, whether it was done on a checked-out folder or
remotely. If I perform a "svn mkdir URL" or "svn cp URL URL" this is
true as it is for "svn propset URL".

Background: Our document release process requires us to check in every
document (PDF) into _one_ directory using a very strict (and
pre-SVN-aged) naming scheme. Additionally, we are not allowed to use the
".pdf" file extension, so autoprops will not work while "svn import"ing
the file to the directory. A simple "svn propset svn:mime-type
application/pdf http://repos/file" would make the day after the import,
but that is not possible, so the whole importing approach does not work.
Instead one has to check out the whole directory (quite some megabytes
of data!) just for being able to set the property of a single added
file. Another solution would be to check out only that single file after
import, but SVN does not support checkout of a single file, only whole
directories (with the only option for subdirectories exclusion) ...

- Matthias

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 28 19:51:37 2006

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

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