> Let me ask you this: if I leave my working binary RPM of
> subversion-1.1.3 alone, get the tarball, untar it, and then follow the
> build instructions for javahl and install that (in other words, a binary
> RPM for subversion itself and a statically linked javaHL) is that a
> workable configuration?
I tried this for days and couldn't get it to work. That said, part of my
problem may have been that I didn't get root to delete
/usr/local/eclipse/configuration, assuming that "eclipse -clean" would
clear the plugin cache. So maybe compiling it statically actually did
work, but I didn't get the Eclipse cache cleared correctly to see it.
Since my system admins didn't want to install Subversion+JavaHL from
source, I had to switch to JavaSVN.
BTW, on SuSe the default svn will corrupt your database if your developers
are accessing it with svn+ssh. You'll need to replace it with a wrapper
script as described in the book.
Either way, you must modify the default RPM installation if you plan on
svn+ssh access. In the end I finally convinced the systems folks to use
the wrapper method on the machine that has the repository.
> I hope someone on the team is devoting some energy to making this easier
> to do.
Hopefully enough people like you and me will ask politely for help. :)
I wonder if it would be possible for svn and svnserve to do "umask 002" by
default? That way we don't need wrapper scripts.
David Coppit firstname.lastname@example.org
The College of William and Mary http://coppit.org/
"Government big enough to supply everything you need is big enough to take
everything you have ... The course of history shows that as a government
grows, liberty decreases." -- Thomas Jefferson
Received on Tue Feb 8 05:04:14 2005