Re: Discussion of SCM_SVN Proposal
| From: | Martin Jansen | Date: | Thu, 15 Apr 2004 20:23:41 +0000 |
| Subject: | Re: Discussion of SCM_SVN Proposal | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-27734@lists.php.net to get a copy of this message | ||
On Thu Apr 15, 2004 at 04:0357AM -0700, Clay Loveless wrote:
> I agree with Tobias' suggestion that SCM_SVN should perhaps be placed under
> "Tools and Utilities" instead of a new SCM category.
I do not feel comfortable with Tools_SVN, but I also do not have a
better idea.
> I've spent a fair amount of time today reviewing the Horde::VC package, as
> well as browsing the current Chora tree. Good stuff, and there's no
> questioning that Chora is a solid and popular application.
>
> My intent with the SVN package is to create a low-level bridge to the
> Subversion command line. (Akin to the way PHP's native low-level MySQL
> functions bridge with MySQL.) Someday, I hope someone with greater C skills
> than mine will take the Subversion C libraries and build a bona-fide PHP
> extension with them. Until then, a PEAR-housed SVN package should act as the
> stand-in. With such a package, any application (or framework) that wants
> easy access to some or all of Subversion's capabilities can include the
> PEAR-housed SVN package.
Can you (in a few words) sum up the differences between your package and
VC?
> I wish I had time to get deeply involved in Horde -- unfortunately, I don't.
> Given the current state of SCM_SVN (roughly 90% feature-complete), it could
> theoretically be dropped into the Horde framework _today_ to beef up the SVN
> side of Horde::VC and Chora. On the other hand, rolling what I've done into
> Horde::VC and then rolling it back out to a new PEAR proposal seems like an
> awful lot of overhead to me.
I do not think there is much overhead: All Horde packages in the
framework/ directory already seem to be "pearified". So packaging them
is more or less only a matter of running "pear package" in the right
directory. In the end the only difference would be that the source code
is not kept on PHP's CVS server but on cvs.horde.org.
Merging your code into Horde's codebase sounds like *the* way to go for
me. Having two version control packages with nearly exactly the same
features would be a pity.
--
- Martin Martin Jansen
http://martinjansen.com/