Re: working with PEAR-CVS code

On Tue, 2002-05-28 at 11:46, Tomas V.V.Cox wrote: > Wolfram Kriesing wrote: > > > > Stig S. Bakken wrote: > > > On Tue, 2002-05-28 at 00:19, Wolfram Kriesing wrote: > > > > > >>this one may be sounds stupid, but i am wondering... > > >>since the directory structure of the finally installed packages and the > > >>one in CVS is different how do you guys work on the code? > > >>a cvs-checkout actually needs to be installed to make it work properly, > > >>or is there an easier way, which lets me also check the code back into > > >>the cvs easily? > > >>do you install every package after updating from the cvs? > > > I certainly don't install everything after updating from CVS. What's > > > the point of that, when you have releases that presumably should have > > > undergone more testing, and that are way more frequent than for PHP > > > itself? :-) > > > > so how do you work with all the packages? since the CVS-structure > > simply is different from the one installed? do you work with links or how? > > see the problem i mentioned with the different xml-packages (i.e RSS, RPC) > > > > I'd recommend to work only in the installed files. Once you have > finished the work on them, just copy them (if you don't want to use "ln > -s") to the package dir and do the commit. Or have a structure in the XML_RSS dir like this (this is what I do): XML_RSS/XML/RSS.php - Stig