Re: Discussion of SCM_SVN Proposal

Quoting Clay Loveless <clay@killersoft.com>:

Overhead for the Chora application, perhaps -- but not for the maintenance/creation of a low level API.

Okay. Best of luck implementing everything from scratch, and I really don't mean that sarcastically - it's often great fun.

Chora is under no obligation to use my package, whether or not it lives in PEAR or doesn't.

Gee, thanks for informing me of that.

The PEAR project _still_ has no version control package, so I think the grounds for my proposal to PEAR -- "Hey, there's not a Subversion package in PEAR! I bet PEAR could benefit from such a package! I'll write a Subversion package for PEAR!" -- are still solid.

I agree. Really, I don't care what happens with this. I've offered, many, many times on the pear mailing lists, to work with anyone interested in using any of the Horde framework packages in PEAR, to give people commit access who want to contribute, to respond to suggestions about independence from other Horde code, etc. If people aren't interested in that, I'm quite happy to crib ideas and bugfixes from other open source code. It's not really duplicate effort for *me*, since I'd have to do the improvements/bugfixes anyway regardless of whether other implementations exist. And relying on yet more PEAR packages really just makes things harder for Horde's users, at least with the current state of things. So maybe having a standalone package is the best way to go. -chuck -- "Regard my poor demoralized mule!" - Juan Valdez