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

Hi Blair.

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

Actually, I'm not trying to do that. What I am trying to do
is to use svn export and svn_load_dirs to "mirror" the contents
of the vendor repository. I don't need all the log information.
When I do the export, it is to a directory which contains the
desired vendor revision as part of its name. So when the Perl
script runs, the commit message has the directory and also the
revision number.

I guess what I'm really trying to do is to mirror a remote
repository. Including the various file properties.

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

I just took a look, and it seems it will not solve my problem.

The problem I am have is the svn export gets everything to the
local system using the local host eol style. So far, so good.
However, when the file is added to the local repository, it will
have the default eol-style. This is the problem.

When a user on a different platform checks out the vendor code
to do a reference build, it will work as long as the platform
used the same eol-style as the platform used for the export/add.
If it does not, the reference build fails. For example, the
export/add is done on a Windows system and the reference build
is done on a Linux system. The Linux build fails.

It looks like SVK might work, but it would depend on whether
it is a jacket for SVN commands (ala Piston) or an interface
to SVN at a lower level. If it is the latter, it could work.

BTW, I have used ClearCase, Perforce, CVS, and several home
grown source control systems so I am familiar with the concepts.

Thanks in advance.

- Mark

---------------------------------------------------------------------
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 15:01:22 CET