[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: state-of-union #2

From: Will Andrews <will_at_physics.purdue.edu>
Date: 2001-09-17 04:44:31 CEST

On Sun, Sep 16, 2001 at 05:56:03PM -0500, Ben Collins-Sussman (sussman@collab.net) wrote:
> * Dale: examine FreeBSD port

Any help I can offer to this end, I'd be glad to put forward.
I'm a FreeBSD Ports developer with two years of experience
"porting" a large variety of things (which has included extensive
autotools hacking), and I'm best known for maintaining the QT/KDE
packages on FreeBSD and generally serving as a FreeBSD/KDE liaison
and more-than-occasional C/C++/Perl hacker.

One of the biggest problems with subversion is that it requires
people to put neon in its subdir.. that can be easily modified
such that instead of doing it that way, subversion can link with
neon's libtool archives in the system libraries. That's the way
it should be done. Same with APR.

Other problems include the rather nasty ac-helper gnu-patch.sh,
which fails on FreeBSD because it's not quite GNU patch, but
supports many of the GNU patch extensions (but FreeBSD does ship
with GNU diff 2.7). Since I don't know the precise details of
what subversion requires from patch(1) and diff(1), I can't
suggest a better approach to checking patch(1)/diff(1) to make
sure they support subversion properly. But likely the approach
would be to actually test some/most of the various features
subversion relies on. I would appreciate if someone provided
information on this.

If we can get these issues sorted out, I'll fast-track a
subversion package/port for FreeBSD. I'm quite eager to use
subversion for my own projects, and the FreeBSD Project has
discussed using subversion for about a year now. :-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:41 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.