quick question about eol-style

[Tucker-10]

I'm having a discussion with the SVN admin at my company about whether
or not you can set eol-style site wide.  He thinks that you can only
do it via $HOME/.subversion/config or per file.  I get the impression
that we can do this in /etc/subversion/config, on the server sdie, and
it will become site-wide.  Since we're using various clients, with
various EOL methods, it would be a big help.  Can someone help me out?
 Bonus points for a doc that says it outright.  I've done some
searching and can't find anything that explicitly defines what can be
used as system options vs what's per client.  (It's entirely likely
that I just missed it.)

--

--tucker

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2423595

Please start new threads on the <users@...> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe@...>.

[Bob Archer]

> I'm having a discussion with the SVN admin at my company about
> whether
> or not you can set eol-style site wide.  He thinks that you can
> only
> do it via $HOME/.subversion/config or per file.  I get the
> impression
> that we can do this in /etc/subversion/config, on the server sdie,
> and
> it will become site-wide.  Since we're using various clients, with
> various EOL methods, it would be a big help.  Can someone help me
> out?
>  Bonus points for a doc that says it outright.  I've done some
> searching and can't find anything that explicitly defines what can
> be
> used as system options vs what's per client.  (It's entirely likely
> that I just missed it.)
>
> --
>
> --tucker

Sorry, your svn admin is correct. But, what you can do is create a pre-commit hook on the server side which will reject any commits that do not have eol-style property set. You can also show your devs how to set up auto-props so when they add new files they automatically get the eol-style property.

I'm pretty sure the svn book explicitly states which config options are server side and which are client side.

BOb

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2423602

Please start new threads on the <users@...> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe@...>.

[Tucker-10]

No need to be sorry.  Someone always has to be wrong.  :)

We've already told the devs how they can set it up client side but I
was hoping SVN would support this globally.  Anything that makes
people do extra thinking comes back to my team as "there has to be a
simpler way."  I'll investigate the pre-submit hook.  I was actually
just looking at them for lint purposes anyway.

I'm sure there's something in the book that I overlooked.  Thanks for the info.

On Mon, Nov 23, 2009 at 1:55 PM, Bob Archer <Bob.Archer@...> wrote:

>> I'm having a discussion with the SVN admin at my company about
>> whether
>> or not you can set eol-style site wide.  He thinks that you can
>> only
>> do it via $HOME/.subversion/config or per file.  I get the
>> impression
>> that we can do this in /etc/subversion/config, on the server sdie,
>> and
>> it will become site-wide.  Since we're using various clients, with
>> various EOL methods, it would be a big help.  Can someone help me
>> out?
>>  Bonus points for a doc that says it outright.  I've done some
>> searching and can't find anything that explicitly defines what can
>> be
>> used as system options vs what's per client.  (It's entirely likely
>> that I just missed it.)
>>
>> --
>>
>> --tucker
>
> Sorry, your svn admin is correct. But, what you can do is create a pre-commit hook on the server side which will reject any commits that do not have eol-style property set. You can also show your devs how to set up auto-props so when they add new files they automatically get the eol-style property.
>
> I'm pretty sure the svn book explicitly states which config options are server side and which are client side.
>
> BOb
>
>

--

--tucker

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2423615

Please start new threads on the <users@...> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe@...>.

[Andrey Repin-3]

Greetings, Tucker!

>>> I'm having a discussion with the SVN admin at my company about
>>> whether or not you can set eol-style site wide.  He thinks that you can
>>> only do it via $HOME/.subversion/config or per file. I get the impression
>>> that we can do this in /etc/subversion/config, on the server sdie, and it
>>> will become site-wide.  Since we're using various clients, with various
>>> EOL methods, it would be a big help.
>>
>> Sorry, your svn admin is correct. But, what you can do is create a
>> pre-commit hook on the server side which will reject any commits that do
>> not have eol-style property set. You can also show your devs how to set up
>> auto-props so when they add new files they automatically get the eol-style
>> property.  
>>
>> I'm pretty sure the svn book explicitly states which config options are
>> server side and which are client side.

> No need to be sorry.  Someone always has to be wrong.  :)

> We've already told the devs how they can set it up client side but I
> was hoping SVN would support this globally.  Anything that makes
> people do extra thinking comes back to my team as "there has to be a
> simpler way."  I'll investigate the pre-submit hook.  I was actually
> just looking at them for lint purposes anyway.

> I'm sure there's something in the book that I overlooked.  Thanks for the info.

No, it's not "pre-submit", it's "pre-commit" hook. And as any hook, it's
running on server side, when data is already submitted to the server, but
before it really committed to the repository.

The simpler way is to create a prototype configuration file and distribute it
across your developers. You could use the very same Subversion for it, as book
explains in one of the examples.


Also, please don't top-post.


--
WBR,
 Andrey Repin (anrdaemon@...) 24.11.2009, <10:48>

Sorry for my terrible english...

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2423704

Please start new threads on the <users@...> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe@...>.

[Ryan Schmidt-66]

On Nov 24, 2009, at 01:52, Andrey Repin wrote:

>>> Sorry, your svn admin is correct. But, what you can do is create a
>>> pre-commit hook on the server side which will reject any commits that do
>>> not have eol-style property set. You can also show your devs how to set up
>>> auto-props so when they add new files they automatically get the eol-style
>>> property.  
>
> The simpler way is to create a prototype configuration file and distribute it
> across your developers. You could use the very same Subversion for it, as book
> explains in one of the examples.

I recommend you do both: create a sample configuration file with auto-props all set up, and write a pre-commit hook that rejects commits that do not conform to the sample configuration file. In the error message you print, direct your users to the sample config file and explain how to install it.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2423714

Please start new threads on the <users@...> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe@...>.