I figured #2 wasn't probably possible but worth asking anyway.
As for #3, I read the manual and wasn't sure whether I was doing this right
or not. I was wondering what the role of /etc/subversion/config was, I got
it to run by restarting Apache. And on my desktop created a new dummy file
to test whether the config rules applied or not, so when I ran svn propget
filename from my desktop, I didn't see any attached metadata. I kinda
guessed this was solely a user thing but wasn't sure and were confused.
Thanks for clearing it up.
We use Perl for all our pre/post commits; is there a perl equivalent file
for the python script you speak of? Otherwise, I'll see if I can dissect
the python script to write my own perl script.
----Original Message Follows----
From: Ryan Schmidt <firstname.lastname@example.org>
To: Res Pons <email@example.com>
Subject: Re: New Server Installation, Access File, and Auto-Props
Date: Sun, 4 Dec 2005 23:34:42 -0600
MIME-Version: 1.0 (Apple Message framework v746.2)
Received: from server20.hostpoint.ch ([18.104.22.168]) by
bay0-mc2-f17.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 4
Dec 2005 21:34:35 -0800
Received: from [22.214.171.124] (helo=[192.168.0.4])by server20.hostpoint.ch
with esmtpa (Exim 4.54 (FreeBSD))id 1Ej8zh-000Hlb-3A; Mon, 05 Dec 2005
X-Mailer: Apple Mail (2.746.2)
X-AntiAbuse: This header was added to track abuse, please include it with
any abuse report
X-AntiAbuse: Primary Hostname - server20.hostpoint.ch
X-AntiAbuse: Original Domain - hotmail.com
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [26 6]
X-AntiAbuse: Sender Address Domain - ryandesign.com
X-OriginalArrivalTime: 05 Dec 2005 05:34:36.0195 (UTC)
On Dec 1, 2005, at 23:17, Res Pons wrote:
>2. I got my access file in conf/ working restricting access and rights.
>Is it possible to block access per file rather per directory? There're
>couple of files in a directory which contians many subdirectories that
>only few authorized users should modify but all other users should have
>r/w access to the subdirectories beneath.
I don't know whether that is possible, sorry.
>3. I'm trying to turn on and enable the auto-props but I don't see
>/etc/subversion being created. Do I manually create this directory? Who
>should be the owner? Root or www? I copied "config, servers, and
>readme.txt" from Windows side to this newly created subdir and tweaked the
>config file and set enable-auto- prop=yes and created [auto-close] with
>file pattern entries underneath it like so *.txt=keyword=Id. Created a
>new text file, checked it in successfully but when I executed "svn
>proplist filename..." I did not see the new properties. Could someone
>please elaborate on this further. Does Subversion automatically and
>magically by default look for /etc/subversion and executes the files? I'm
>lost and this part is not working for me.
auto-props are a client-side thing, not a server-side thing. The clients
need to set up their config files with the auto-props they want. Any config
file in /etc/subversion is merely used as the default for clients running
on that same computer who don't have a custom config file in their own
Subversion directories. So unless your users are logging in to the
Subversion repository server with SSH (which you said they're not) then an
/etc/subversion directory on the repository server won't do anything for
What you should do is create a standard config file and distribute it to
your users. Then you should install a pre-commit hook on the server which
verifies committed files against that master config file, and rejects
commits that do not comply. I recently posted a link to a Python script
that someone had written for this purpose.
Donít just search. Find. Check out the new MSN Search!
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Dec 5 18:55:41 2005