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

Re: SVN doesn't like .so files?

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Fri, 10 Oct 2014 15:28:27 -0500

On Fri, Oct 10, 2014 at 2:56 PM, James <oldyoungguy88_at_yahoo.com> wrote:
> After I "import", I have renamed my project folder to project.bak folder and
> created a new empty project folder. I found this after I do "co" in my new
> project folder.
> How can I easily add these .so files or other possible ignored files into
> repository? There are about 900MB data (JDK and Eclipse). I don't want to
> miss any files.

First, make sure this is really what you want to do. Normally you
would only want 'source' type files that you would check out in
working copies so you can edit and rebuild any binaries from them. If
you do need some unrelated fixed-version binaries brought along with
every checkout, consider putting them elsewhere (in the same or a
different repository) and using svn:external properties to pull any
tools or supporting libraries into their own subdirectories of the
working space. That way you can separate the versioning of 'your'
project from any separately-managed support tools/code/binaries. If
you subsequently commit new versions of the tools/libs, you can
control the checked-out version by using peg-revision syntax or tag
copies for your external targets.

> 1. Can I delete the new project folder and rename back the project.bak, and
> then use "svn add ."?


> or
> 2. Copy entire contents of project.bak folder (has ALL files) into the new
> project folder (missing some files), and then do "svn add ."?

Yes. If you are sure you really want that.

> Does the "svn add ." can find new files and ignore existing files to add
> onto repository, after commit?

I'm not sure if the svn:ignore becomes a remembered property after the
first run or if it is strictly a client setting. You'll be able to
tell by what the svn add command shows, though. If it isn't taking
them, explicitly putting the filenames on the command line will work
and, at least on unix-like systems you can use wildcards like * */*
*/*/*, etc,. to have the shell expand all the filenames for you.

   Les Mikesell
Received on 2014-10-10 22:35:39 CEST

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.