Question re auto-props example in config file

[Kylo Ginsberg <ky...@gmail.com>]

The default .subversion/config file contains some helpful examples in
the auto-props section.  Here's a snip:

*.c = svn:eol-style=native
*.dsp = svn:eol-style=CRLF
Makefile = svn:eol-style=native

My question is: why single out *.dsp for an svn:eol-style of CRLF?

By way of background, I have a lot of directories representing
libraries built both with Visual Studio in a Windows environment and
with gnu tools in a Unix environment.  So a sample directory might
include:

lib/foo.c
lib/Makefile
lib/foo.dsp

My thinking would be to make all 3 of these files, .dsp included, set
svn:eol-style to native.  That way, a developer on either side needing
to make a simple mechanical change (e.g. renaming foo.c to foo1.c)
could edit both respective build files in their env, and check them in
safely.

But the sample config singles out *.dsp.  Am I missing something?  Is
there a workflow where it would cause troubles if these are all set to
native?

Thanks,
Kylo

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

Re: Question re auto-props example in config file

[Thomas Heller <th...@ctypes.org>]

Kylo Ginsberg schrieb:
> 
> For reference, is there a list of what filetypes *must* have CRLF line
> endings for Visual Studio?  The example config file specifies
> svn:eol-style as CRLF for the .dsp and .dsw extensions, but specifies
> "native" for .c, .h, .cpp.  How about .rc, .rc2, .vcproj, ...?

I do not know a complete list, but I know that .vcproj and .sln files
*can* use native line endings (they are a kind of XML format), while source files
like .c, .h, .cpp, as well as .rc .rc2 should be text files and probably
*should* use native.

Thomas

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

Re: Question re auto-props example in config file

[Kylo Ginsberg <ky...@gmail.com>]

On 3/1/07, Thomas Heller <th...@ctypes.org> wrote:
> Kylo Ginsberg schrieb:
> > The default .subversion/config file contains some helpful examples in
> > the auto-props section.  Here's a snip:
> >
> > *.c = svn:eol-style=native
> > *.dsp = svn:eol-style=CRLF
> > Makefile = svn:eol-style=native
> >
> > My question is: why single out *.dsp for an svn:eol-style of CRLF?
> >
> > By way of background, I have a lot of directories representing
> > libraries built both with Visual Studio in a Windows environment and
> > with gnu tools in a Unix environment.  So a sample directory might
> > include:
> >
> > lib/foo.c
> > lib/Makefile
> > lib/foo.dsp
> >
> > My thinking would be to make all 3 of these files, .dsp included, set
> > svn:eol-style to native.  That way, a developer on either side needing
> > to make a simple mechanical change (e.g. renaming foo.c to foo1.c)
> > could edit both respective build files in their env, and check them in
> > safely.
> >
> > But the sample config singles out *.dsp.  Am I missing something?  Is
> > there a workflow where it would cause troubles if these are all set to
> > native?
>
> Visual Studio refuses to load .dsp files that have the wrong line endings;
> so this setup is entirely correct.  Problems would occur with native line
> endings if you build a source tarball on a Linux platform, and try to use that
> on a Windows machine.
>
> Thomas

OK, good to know the rationale.  In our workflow, source is never
distributed by tarball, but I can see where that could be a nice
feature.

For reference, is there a list of what filetypes *must* have CRLF line
endings for Visual Studio?  The example config file specifies
svn:eol-style as CRLF for the .dsp and .dsw extensions, but specifies
"native" for .c, .h, .cpp.  How about .rc, .rc2, .vcproj, ...?

Kylo

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

Re: Question re auto-props example in config file

[Thomas Heller <th...@ctypes.org>]

Kylo Ginsberg schrieb:
> The default .subversion/config file contains some helpful examples in
> the auto-props section.  Here's a snip:
> 
> *.c = svn:eol-style=native
> *.dsp = svn:eol-style=CRLF
> Makefile = svn:eol-style=native
> 
> My question is: why single out *.dsp for an svn:eol-style of CRLF?
> 
> By way of background, I have a lot of directories representing
> libraries built both with Visual Studio in a Windows environment and
> with gnu tools in a Unix environment.  So a sample directory might
> include:
> 
> lib/foo.c
> lib/Makefile
> lib/foo.dsp
> 
> My thinking would be to make all 3 of these files, .dsp included, set
> svn:eol-style to native.  That way, a developer on either side needing
> to make a simple mechanical change (e.g. renaming foo.c to foo1.c)
> could edit both respective build files in their env, and check them in
> safely.
> 
> But the sample config singles out *.dsp.  Am I missing something?  Is
> there a workflow where it would cause troubles if these are all set to
> native?

Visual Studio refuses to load .dsp files that have the wrong line endings;
so this setup is entirely correct.  Problems would occur with native line
endings if you build a source tarball on a Linux platform, and try to use that
on a Windows machine.

Thomas

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