On Mon, Sep 17, 2001 at 07:15:40PM -0400, Garrett Rooney wrote:
> On Mon, Sep 17, 2001 at 11:00:34PM +0100, Joe Orton wrote:
> > I'd advise using the bundled copy of neon in your SVN port until the
> > neon API is stable, unless you are prepared to deal with API
> > compatibility issues.
>
> it depends how unstable the neon api is... the only real reason i
> wanted to move to the ports version of neon is that currently my port
> installs the neon-config binary over the top of the one which is
> installed on the system already. if you think it would be better (for
> now anyway) to just hack around this in the port, i can certainly do
> that.
>
> how much has the neon API been changing lately? is it a lot, or are
> you just trying to keep your options open until neon hits 1.0?
It has changed on practically every release. Sometime, in an incompatible
fashion which requires a decent amount of client change. Note that even
Joe's own "cadaver" program is stuck back on Neon 0.12 because it hasn't
been upgraded.
That said, SVN is using the latest Neon, so if your port can require a
specific revision (0.15.3), which happens to be the latest, then we should
probably be okay. And SVN will more than likely track Neon pretty quickly.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
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