Thanks for the solution.
Sorry about duplicating threads, it's very hard to find anything useful with
".so" as one of the search terms.
Yes we definately want to keep binaries in one of our repositories. We are
using separate repos for managing different projects, but we have one which
actually keeps copies of the installed apps which trivialises the way we
upgrade our servers.
At the moment we are not in the position to be creating packages for our OS
so managing it in SVN or similar is the perfect solution given our
2009/5/26 Konstantin Kolinko <knst.kolinko_at_gmail.com>
> 2009/5/26 Tyler Roscoe <tyler_at_cryptio.net>:
> > On Mon, May 25, 2009 at 05:24:28PM -0700, David Schoen wrote:
> >> I am using svn to maintain some binaries in addition to the source used
> to build them.
> >> When I add a directory using "svn add" all .so files appear to be
> >> Is there some property I can set/unset to ensure that .so files are not
> just skipped?
> > 1. Keeping the compiled libraries in your VCS is a questionable
> > practice. Are you sure this is what you want to do?
> > 2. See
> > and look for global-ignores.
> Warning: There is an error in the book:
> The default value of global-ignores was changed in svn 1.5 and
> now includes *.so *.so.[0-9]* files,
> but the one displayed in the book was not updated.
> Your solution is to explicitly specify some value for the global-ignores
> in the configuration file. Using an empty string disables the defaults:
> Some previous threads on this issue:
> Best regards,
> Konstantin Kolinko
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-27 01:22:56 CEST