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

Re: Some XML Questions

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-02-02 20:37:45 CET

On Fri, Feb 02, 2001 at 08:52:24AM -0600, Karl Fogel wrote:
> Sam TH <sam@uchicago.edu> writes:
> > Patch for the comment. (How can I make ediff respect .cvsrc?)
> Applied (thanks!).
> Re expat-lite vs tracking expat:
> The minute we need something expat-lite doesn't give us, we should
> upgrade and probably start tracking the live expat. But to do so
> before then would be fixing what's not broken, and that always risks
> causing bugs. There's no point making trouble for ourselves.

Here's a minute:

1) we cannot (dynamically) link expat-lite into a process which includes
   another copy of Expat or expat-lite.

2) our use of libtool 1.3 currently prevents us from defining library-to-
   library dependencies. but when libtool 1.4 comes out, we will. at that
   point, we'll mark libsvn_subr as dependent upon a version of Expat.

3) mod_dav_svn uses libsvn_subr, which means it depends on Expat. that
   cannot be expat-lite because of (1) above.

Today, mod_dav_svn happens to work because I rely on Apache's expat-lite to
satisfy the needs of libsvn_subr. All of this is asking for trouble down the
line. Simplifying management of this stuff will steer us towards the most
recent Expat, rather than our own copy.

Note that we should probably track releases of Expat rather than the CVS
version. When we ship, we need to work against a release... not CVS.
APR(UTIL) does not have a formal release at this point, so we aren't doing
that. It is also an alpha/beta product still seeing changes, so tracking
them via CVS is best.

[ and note that we don't track Neon via CVS because it isn't on a public CVS
  share for logistical / Joe-productivity reasons. ]


Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:21 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.