My first comment is that storing intermediate binary files (like .o and .pyc) in Subversion is fairly irregular and not something I would recommend. My approach is that if it can be generated from the source, it probably shouldn't be in version control, particularly binary files which are platform-specific. However, it's your repository and I'll assume you know what you're doing. :-)
The first thing I would check is whether you can add the files from Terminal,
with the 'svn add' command. My suspicion is that you probably cannot. That
would lead me to check your ~/.subversion/config file, which governs how *all*
Subversion clients you may use will react. Notably, there is a "global-ignores"
setting which ignores files which match patterns which should be excluded; for
example, here is the default:
global-ignores = *.o *.lo *.la #*# .*.rej *.rej .*~ *~ .#* .DS_Store
It's possible that you may have *.pyc and *.so in that list as well — that's
the easiest explanation for why SVN wouldn't add such files (and wouldn't
display them in 'svn status' output, either).
Hope that helps,
- Quinn
On Dec 16, 2010, at 8:05 AM, madscatt wrote:
> Hi,
>
> I am using versions 1.1.2 (SVN 1.6.15) on a Mac Pro (OS X 10.6.4). I
> have attempted to import a directory that contains many python files
> (both *.py and *.pyc) and various C files (*.c) and their objects (*.o
> & *.so). The python and C files import fine. The "binary" files are
> not imported (*.o, *.so, and *.pyc). Executable binaries in other
> folders are imported okay. I have checked the read-write permissions
> and I can SEE the files in the folder. Do all binaries have to be
> designated executable to be imported?
>
> This worked okay for me in a previous version of the software (I
> routinely kept *.pyc and *.o/*.so files in the repository). This
> repository still exists with the binary files but I don't want to
> touch it since I don't want to lose the files that are there.
>
>
> -rw-r--r-- 1 curtisj staff 4271 Oct 14 10:20 benergy.py <------
> imports fine
> -rw-r--r-- 1 curtisj staff 1912 Mar 26 2009 overlap.c <------
> imports fine
> -rw-r--r-- 1 curtisj staff 2444 Mar 26 2009 overlap.o <------ is
> NOT imported
> -rwxr-xr-x 1 curtisj staff 7752 Mar 26 2009 overlap.so* <------
> is NOT imported
> -rw-r--r-- 1 curtisj staff 3875 Dec 8 14:36filterparam.pyc <
> ------ is NOT imported
> -rwxr-xr-x 1 curtisj staff 31638 Mar 26 2009 xtal2sas.exe* <------
> imports fine
>
>
> There is no mention of the files in the transcript (a portion of which
> is attached):
>
> Adding
> '/Users/curtisj/Desktop/sassie/simulate/protein/monomer/benergy.py'
> Adding
> '/Users/curtisj/Desktop/sassie/simulate/protein/monomer/overlap.c'
> Adding
> '/Users/curtisj/Desktop/sassie/simulate/protein/monomer/filterparam.py'
> Adding
> '/Users/curtisj/Desktop/sassie/simulate/protein/monomer/nbenergy.py'
> ...
> Adding (BIN) '/Users/curtisj/Desktop/sassie/calculate/xtal2sas.exe'
>
> --
> You received this message because you are subscribed to the Google Groups
> "Versions" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/versions?hl=en.
>
smime.p7s
Description: S/MIME cryptographic signature
