Setting up the Configuration File

["Weintraub, David" <Da...@ilex.com>]

We have recently established a policy that one of our project will allow for
automatic keyword expansion for $Id$. This is not true for other projects.
I understand that I can set this in the "config" file by putting in the
following lines:
[miscellany]
enable-auto-props = yes

 [auto-props]
* = svn:keywords=Id

I also understand that the default Subversion config file is
/etc/subversion/config.

What concerns me is that we have two projects, one where we want to allow
all users to have $Id$ keyword expansion and in another project, we do not
necessarily want to enable this expansion. Both projects are using the same
Apache webserver but two different archives.

I am also concerned that the /etc/subversion/config directory is for the
clients that are on that machine and not the clients who may not be on that
machine, but use the Subversion archive on that machine.

How do I set up our archive so that http://switchblade/project1
automatically allows all files to have $Id$ keyword expansion while
http://switchblade/project2 doesn't do that?

Re: Setting up the Configuration File

[William Nagel <bi...@stagelogic.com>]

On Mar 29, 2005, at 3:00 PM, Weintraub, David wrote:

> We have recently established a policy that one of our project will 
> allow for automatic keyword expansion for $Id$. This is not true for 
> other projects.
>
> I understand that I can set this in the "config" file by putting in 
> the following lines:
> [miscellany]
> enable-auto-props = yes
>
>  [auto-props]
> * = svn:keywords=Id
>
> I also understand that the default Subversion config file is 
> /etc/subversion/config.
>
> What concerns me is that we have two projects, one where we want to 
> allow all users to have $Id$ keyword expansion and in another project, 
> we do not necessarily want to enable this expansion. Both projects are 
> using the same Apache webserver but two different archives.

As far as I know, there is no way to direct enable-auto-props to a 
specific repository.

>
> I am also concerned that the /etc/subversion/config directory is for 
> the clients that are on that machine and not the clients who may not 
> be on that machine, but use the Subversion archive on that machine.

The 'config' file is a user configuration file that configures the 
behavior of the svn client, not the repository.  /etc/subversion/config 
sets defaults for all of the clients local to a given machine, but that 
default can be overridden by each individual user's ~/.svn/config file.

>
> How do I set up our archive so that http://switchblade/project1 
> automatically allows all files to have $Id$ keyword expansion while 
> http://switchblade/project2 doesn't do that?

There really isn't any good way to do what you want to do.  One 
possible hack would be to give all of your users a special script for 
doing file adds that would wrap the 'svn add' command and automatically 
perform the property addition if the file is being added to project1.  
It would be a bit of a pain, since you'd have to distribute special 
scripts/binaries to each user, and it would also be a little bit 
error-prone, since users would still be able to use 'svn add' by 
itself.  If you really need the auto-props differentiation, though, it 
may be a workable solution.

Hope that helps,

-Bill


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org