Re: Enlighten about new SVN

Martin Jansen wrote: > techtonik wrote: >> Did you thought about making http://pear.php.net to be >> Apache-based >> cluster >> with distributed DB-machines for each kind of serious application and >> distributed NFS for storage? > > Nope. These are all pretty buzzwords which I can translate for you into a single fact: PEAR has no need for this kind of performance zooming, we are using about 2% of the box (both CPU and disk space) that we have at pear.php.net, and we also have mirrors at us.pear.php.net and de.pear.php.net for installation. All of PEAR's web resources are generously donated by Pair Networks, Bluga.net and Cweiske.de. >> I've seen some notes here about luring developers back to PEAR. These >> seemed >> somehow related to SVN. Have you tried to put a voting about what would >> people prefer to live and develop PEAR republic - i.e. "CVS, SVN or Do >> not >> care"? > > Nope. The single most requested feature over the past 2 years has been for an SVN repository, and since implementing, not one person has complained. >> To make a patch you need to make checkout, copy your patched directory >> tree >> over it and then build a diff. Since I was too lazy to install CVS tools >> right away I though I could wait another week to do this in SVN, but >> since >> you do not have any plans or goals or roadmaps on when it could be >> implemented, I doubt it will ever happen. I can help you with SVN >> setup if >> you can show where the main problem is. > > I don't think there are technical problems. I agree with your > assumption that a transition from CVS to Subversion for peardoc isn't > going to happen anytime soon. Get yourself a proper CVS setup and > everything is fine. :) I wonder how you got a copy of the source of peardoc without using CVS? This would be more onerous than the 2-liner: cvs -d :pserver:cvsread@cvs.php.net:/repository login cvs -d :pserver:cvsread@cvs.php.net:/repository co peardoc and then edit peardoc source and the hard part: cvs diff -u > patch.txt The above commands assume unix. Windows is easy even if you don't have tortoisecvs installed (again - tortoisecvs.org, click download, run installer, reboot, right-click in explorer and do checkout, edit, then right click and choose "make patch" and you're good to go) Is there a problem that needs solving? Greg