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

Re: Making ra_serf the default for DAV

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2006-10-20 00:00:49 CEST

On Thu, Oct 19, 2006 at 05:13:26PM -0400, John Szakmeister wrote:
> ----- Justin Erenkrantz <justin@erenkrantz.com> wrote:
> > On Thu, Oct 19, 2006 at 06:30:48PM +0200, Stefan Kng wrote:
> > > serf also misses the progress callback neon has, which is an important
> > > feature for GUI clients. Making it the default for DAV may work ok for
> > > the command line client, but for me as the dev of TSVN I would keep
> > > using neon for that reason.
> >
> > It's not like serf is set in stone. If you can tell me what you would be
> > looking for, we might be able to add it or rather I can help you create the
> > patches. =) -- justin
> Along these lines, I'd like us to be able to build serf without the entire apr source tree. I'd like to use my system's apr libraries, rather than having to compile my own or rebuilding the system ones just so that I have a good source tree.
> You may have addressed this issue already (I haven't tried in a while), but it was a showstopper for me, and possibly for other package maintainers.

Use serfmake instead of the autoconf-based system.

$ ./serfmake install

If apr-1-config and apu-1-config aren't in your PATH, use
--with-apr=/path/to/apr - if they are present, serfmake will just work(TM).

If you are building from a checkout and using ./buildconf + ./configure
(instead of serfmake), then you need apr and apr-util source to grab the m4
macros - but httpd has the same source requirements. (And, when I cut a
release, you won't need to run ./buildconf either - ./configure is enough.)

HTH. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 20 00:01:06 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.