Re: state-of-union #2

 
> 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.

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. but if you'd prefer to stick with your current build process
for now (until neon stabalizes) i can just have the port hack around
the few real problems i have with the current stuff.

-- 
garrett rooney                     Unix was not designed to stop you from 
rooneg@electricjellyfish.net       doing stupid things, because that would  
http://electricjellyfish.net/      stop you from doing clever things.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org