On Tue, Sep 18, 2001 at 07:53:47AM -0400, Garrett Rooney wrote:
>
> > 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.
>
> well, i can require a specific version of neon, it just means that
> future upgrades of the version of subversion in the ports tree would
> have to wait until the neon in the ports tree is updated. that
> shouldn't be an issue though. if the version of neon isn't being
> upgraded quickly we could just have a neon-latest port like they have
> for berkely db.
That sounds great.
> so i guess if you guys are willing to accept patches to let subversion
> build with an out of tree neon, i would still be willing to write
> some.
Definitely; please do!
joe
---------------------------------------------------------------------
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