You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by James <ol...@yahoo.com> on 2014/10/10 20:19:52 UTC
SVN doesn't like .so files?
I am trying to add an existing project into the SVN repository. It seems work but when I check them out in a new location, I found all .so files are not present. Then I look at the repository, these .so files from JDK are not there.
Any workaround? I am using 1.8.10(r1615264) svn. The command I used to add project is "svn import -m "my message" . svn://homeNetworkIP/repositoryName".
Please help,
Thanks,
James
Re: SVN doesn't like .so files?
Posted by Les Mikesell <le...@gmail.com>.
On Fri, Oct 10, 2014 at 1:19 PM, James <ol...@yahoo.com> wrote:
> I am trying to add an existing project into the SVN repository. It seems
> work but when I check them out in a new location, I found all .so files are
> not present. Then I look at the repository, these .so files from JDK are
> not there.
>
> Any workaround? I am using 1.8.10(r1615264) svn. The command I used to add
> project is "svn import -m "my message" .
> svn://homeNetworkIP/repositoryName".
>
The client where you committed was most likely configured to ignore
*.so files (and other common binary build results). You can override
this by explictly doing an 'svn add' of missing files and committing
them, or you can change the client configuration if you want different
default behavior.
--
Les Mikesell
lesmikesell@gmail.com
Re: SVN doesn't like .so files?
Posted by Les Mikesell <le...@gmail.com>.
On Fri, Oct 10, 2014 at 2:56 PM, James <ol...@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 ."?
No.
> 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
lesmikesell@gmail.com
Re: SVN doesn't like .so files?
Posted by James <ol...@yahoo.com>.
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.
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 ."?
Does the "svn add ." can find new files and ignore existing files to add onto repository, after commit?
Thanks,
James
On Friday, October 10, 2014 2:35 PM, David Chapman <dc...@acm.org> wrote:
On 10/10/2014 11:19 AM, James wrote:
I am trying to add an existing project into the SVN repository. It seems work but when I check them out in a new location, I found all .so files are not present. Then I look at the repository, these .so files from JDK are not there.
>
>
>Any workaround? I am using 1.8.10(r1615264) svn. The command I used to add project is "svn import -m "my message" . svn://homeNetworkIP/repositoryName".
>
>
>Please help,
>
>
>Thanks,
>James
>
Look in "~/.subversion/config", section "[miscellaneous]" for
"global-ignores". This is a listing of files that are ignored by
default when you import a directory. You can add any file manually,
but derived files like "*.o", "*.so", and "*.exe" (Windows) are
often not added to the repository and so they tend to be omitted
from automated processes.
You can of course change the configuration file so that "*.so" files
are not automatically excluded.
-- David Chapman dcchapman@acm.org Chapman Consulting -- San Jose, CA Software Development Done Right. www.chapman-consulting-sj.com
Re: SVN doesn't like .so files?
Posted by David Chapman <dc...@acm.org>.
On 10/10/2014 11:19 AM, James wrote:
> I am trying to add an existing project into the SVN repository. It
> seems work but when I check them out in a new location, I found all
> .so files are not present. Then I look at the repository, these .so
> files from JDK are not there.
>
> Any workaround? I am using 1.8.10(r1615264) svn. The command I used to
> add project is "svn import -m "my message" .
> svn://homeNetworkIP/repositoryName".
>
> Please help,
>
> Thanks,
> James
Look in "~/.subversion/config", section "[miscellaneous]" for
"global-ignores". This is a listing of files that are ignored by
default when you import a directory. You can add any file manually, but
derived files like "*.o", "*.so", and "*.exe" (Windows) are often not
added to the repository and so they tend to be omitted from automated
processes.
You can of course change the configuration file so that "*.so" files are
not automatically excluded.
--
David Chapman dcchapman@acm.org
Chapman Consulting -- San Jose, CA
Software Development Done Right.
www.chapman-consulting-sj.com
Re: SVN doesn't like .so files?
Posted by jb...@icloud.com.
On Oct 10, 2014, at 11:19 AM, James <ol...@yahoo.com> wrote:
> I am trying to add an existing project into the SVN repository. It seems work but when I check them out in a new location, I found all .so files are not present. Then I look at the repository, these .so files from JDK are not there.
>
> Any workaround? I am using 1.8.10(r1615264) svn. The command I used to add project is "svn import -m "my message" . svn://homeNetworkIP/repositoryName".
>
> Please help,
>
> Thanks,
> James
By default, subversion will ignore .so files, since those are derived by compiling source files. If you performed "svn add" specifying a directory, the .so files would not have been included. If you really want to include .so files, you can explicitly add them.
To see what subversion has ignored, you can do "svn status --no-ignore".
Global ignores are configured in ~/.subversion/config in the "miscellany" section, using the global-ignores property.