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

Re: Questions from the Subversion 1.6 Preview event in Berlin

From: <kmradke_at_rockwellcollins.com>
Date: Wed, 25 Feb 2009 15:59:06 -0600

> wc-ng
> ~~~~~
> There was a sort of eerie concern about wc-ng, in that it will change
> basic properties of working copies on disk. There was mention of some
> zipping whole working copies and sending them by Email, or storing them
> for later committing. Our general reply to those remarks was "use
> but people were insistent that some users will not be happy with making
> use of working copies any more complex by adding restrictions. Needing
> announce the rename or deletion of a working copy to a central database
> could, in essence, break a lot of people's workflow, blocking an
> After stsp broke down the main reasons for and benefits of wc-ng
> sanity, speed, concurrency, complex queries), there was some sort of
"ok, we
> understand now". But, ...

As a corporate user I welcome a working copy rewrite. I'm assuming
there is a "central database" for each working copy, so one could still
zip up the directory tree and mail it. I don't think this is as
bad as you made it sound.

> - We were again asked about svn obliterate. How far are the plans?
> Is it going to come any time soon?

This is almost a must for corporate users, since completely dumping
my largest 150G repo, filtering it, and reloading it would probably
be impractical if not impossible.

> - We were again asked about server-imposed rights restrictions.
> This time the wish was to "at least" be able to forbid certain
> operations in certain directories. Our gut answer was:
> use commit hooks. Anything to add here?

The biggest problem is the disconnect between the different
authentication and authorization steps. For example, if you use
apache and ldap, you can easily map group members to repository access.
But if you also need directory level restrictions you then must pull
data out of ldap into a special authz file. If you then need
to restrict certain operations via a hook script, you must then
pull data out of ldap into a special restrictions file. Thus you
now have 3 potentially separate configuration areas that you
must manually keep in sync.

Kevin R.

Received on 2009-02-25 22:59:25 CET

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.