Re: practical concerns for moving PEAR forward
| From: | Greg Beaver | Date: | Sun, 01 Oct 2006 01:19:14 +0000 |
| Subject: | Re: practical concerns for moving PEAR forward | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-44219@lists.php.net to get a copy of this message | ||
Jon Parise wrote:
> On Thu, Sep 28, 2006 at 01:08:27PM +0900, Ian Warner wrote:
>
>
>>Seems to be that a major issue with the PearWeb is its ties with the
>>php.net CVS system.
>>
>>1. Whats stopping PEAR breaking away from php.net CVS. And setting up on
>>a new server with SVN powering it?
>
>
> Why do you suspect the current CVS implementation is causing problems
> with the PEAR web site? Subversion, while probably superior to CVS,
> doesn't seem like a solution to any of the current big ticket items.
Hi,
To clarify, it isn't. The problem is the way that pear.php.net is
synchronized from CVS. Using SVN would cause the identical problem.
What we need is to make it possible to sync from a release rather than
directly from source control. This is why I'm working on making the
website PEAR-installable.
This way, should a new release break the website, we can revert to the
previous version in a flash with:
pear upgrade --force pearweb-1.2.3.tgz
(assuming 1.2.3 is the old version)
Greg