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

Re: Default eol styles

From: Martin Furter <mf_at_rola.ch>
Date: 2004-01-10 22:30:57 CET

On Sat, 10 Jan 2004, Casper Hornstrup wrote:
> > -----Oprindelig meddelelse-----
> > Fra: Erik Huelsmann [mailto:e.huelsmann@gmx.net]
> > Sendt: 10. januar 2004 19:42
> > Til: Casper Hornstrup
> > Cc: dev@subversion.tigris.org; users@subversion.tigris.org
> > Emne: Re: Default eol styles
> >
> >
> > [ snip proposal for new property ]
> >
> > Casper,
> >
> > I'm sorry to snip your complete proposal, but did you look at
> > the configuration file of recent Subversion versions? On
> > Windows it's located in %APPDATA%\Subversion\config (Windows
> > guru's: did I specify this correctly?). For my useraccount
> > it's at c:\Documents and Settings\Erik\Application
> > Data\Subversion\config.
> >
> > In the [auto-props] section you can define behaviour which
> > does almost what you want in sofar that it is the same, but
> > client-side. I donīt know whether TortoiseSVN or RapidSVN
> > actually use that file, but if they use (and I believe they
> > do) the libsvn_client library to take care of Subversion
> > interaction they can provide the same functionality. That
> > library has this functionality built into it, so that any
> > client (be it on Windows or Unix) just has to supply these settings.

If you want to use auto-props don't forget to enable them:
enable-auto-props = yes

> I did find the [auto-props] feature in the archives (I couldn't
> figure out if it was implemented on Windows though). I don't like
> it for the following reasons:
> 1) Its a per user configuration. Every user must configure these
> rules and it is easy to forget this. If the rules change, then
> all users have to change their configuration. Do they remember
> this and will they do it when asked so there will be no problems
> caused by forgetting this when they commit later? What if a user
> missed the information on the change of rules?
You can store the subversion config in a subversion repository (i think
that's th reason why it is ~/.subversion on UNIX and not ~/.svn).

> 2) Its an all or nothing approach. You can't make exceptions to the
> rule so all projects you work on, on a particular computer, will
> use the same rules. If you work on two projects that have a
> conflict in the rules you either need to use two user accounts,
> manually change the configuration file, or remember the rules and
> apply them manually. I'd much rather have Subversion remember and
> apply the rules I've setup for me.
No, the config directory can be specified with --config-dir for the
commandline client. But ofcourse you'd have to remember always specifying
the right config.
I don't know if other clients support that feature too.

> 3) Its not safe. When the rules are on the client computer they can
> get lost by a format and/or reinstall. When the rules are in the
> repository, they don't get lost.
Yeah, but other information then also gets lost, f.ex. the network
configuration (yeah, i know that DHCP partially solves this) or
configuration of other apps.
I propose the same solution as for 1).

Ofcourse i also would like to have this configuration stored in the
repository and used only for that repos.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 10 22:32:16 2004

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.