Konstantin Kolinko wrote:
> 2008/11/1 Ryan Schmidt <subversion-2008c_at_ryandesign.com>:
>> On Oct 31, 2008, at 16:16, Miller, Hugh wrote:
>>> I've started using svn 1.5.2. It doesn't seem to import or commit shared
>>> object lib files or archives (e.g., lib…something.so or lib…something.a).
>>> Have things changed in this regard for 1.5.2 ? This used to work in 1.4.3
>> Nothing should have changed. Subversion has no built-in prejudice against
>> (nor even any built-in knowledge of) any filetypes.
> No, it has.
> The default value for the global-ignores option is not empty.
Uh, the default value for global-ignores *is* empty. See below...
> The value can be seen in the sources (as some #define there), and
> is also written as a comment into the subversion config file when
> it is auto-created for the first time.
> In svn 1.5.0 it is
> # global-ignores = *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a *.pyc *.pyo
> # *.rej *~ #*# .#* .*.swp .DS_Store
These lines are commented out, and have no bearing on the default operation of
Subversion. Of course, if you choose to uncomment them, or an administrator
does, these patterns will be ignored, but it isn't the default setting.
> Note, that the value differs between svn 1.4 and 1.5. That is, you should
> start with empty configuration files to get them rewritten and to see
> the recent value of comment, or look into the sources.
> The default value for 1.5 includes pattern for *.so files, while the one
> of 1.4 does not, and I was once caught by the change.
I think the only file type the Subversion ignores out-of-the-box is .o files
(but certain other generated binary types may there also). To see what is being
ignored, run: 'svn st --no-ignore'. Also, just because a file is being ignored,
does *not* mean you can't manually add it. After adding it using 'svn add', it
will be treated like all other versioned files.
Received on 2008-11-01 14:43:31 CET