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

Re: Vendor drops, svn_load_dirs.pl, and eol-type

From: Blair Zajac <blair_at_orcaware.com>
Date: Thu, 14 Feb 2008 20:06:17 -0800

On Feb 14, 2008, at 12:50 PM, L. Mark Pilant wrote:

> Greetings.
>
> I'm getting bit by an "anomaly" trying to correctly handle vendor
> drops.
>
> The problem is the repository from which I am obtaining the vendor
> code has several files with the svn:eol-style set to "native". I
> would like to keep this property for the files as they exist in
> my repository.
>
> However, when I do an export to pick up the vendor code, knowledge
> of this property is lost. Thus when I use svn_load_dirs.pl to add
> this new drop to my repository svn:eol-style is the default (not
> set to anything) which causes builds to work or fail depending on
> whether the builds are being done on *nix or Windows. If it were
> only *nix or Windows there wouldn't be a problem; but I need to be
> able to support multiple platforms.
>
> There are thousands of files I need to bring over, so even writing
> a script to look at each file from the vendor's repository and set
> the property correctly on my repository is not very appealing.
>
> Any thoughts or suggestions?
>
> Thanks in advance.
>
> - Mark

You can try the piston tool if you are mirroring a remote svn
repository in your own.

http://piston.rubyforge.org/

svn_load_dirs.pl wasn't designed to mirror a checkout from another
repository.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<blair_at_orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-15 05:06:34 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.