Re: [RFC] CVS directory structure

I am -1 on the proposal too. Don't see the point of it. If the problem it tries to solve is that it makes it easy to test on a local CVS checkout, is it really that difficult to have: // include_once 'Foo/Bar/Boing.php'; include_once 'Foo_Bar/Boing.php'; That is what I usually do, and keep the pear checkout dir in my include_path. Easy and no need to rearrange existing packages, or create artificially deep dir trees as in part 2 of the proposal by Tobias. When you are about to release, change the comments (or remove them) and then change your package.xml. If you do have lots of dependencies, then you should be keeping the package.xml up to date and doing installs from your CVS code when testing (that way you do not need to keep track of the include_once). I use that approach too for other package I maintain. Am I missing something that cannot be accomplished with the approaches above. I tend to favor a K.I.S.S. approach when thinking about development, perhaps my experience is too simplistic, but works for me. --- Tobias Schlitt <tobias@schlitt.info> wrote: > On Sat, 2003-11-15 at 16:13, Pierre-Alain Joye wrote: > > > > > I'm -1 on this. CVS is a tool for source control. Doing development > > > > directly > > > > on your CVS dir is a bad idea. > > > > That's exactly the point. CVS is initially made for developing inside > > > it's checkout directories. That's just your local copy, which you will > > > commit to the central repository. So copiing files away from your > > > sandbox nd recopiing is double effort, without win. > > > Developing here == keeping files history, not run them. Nothing more. > > > pear install package.xml should be used, or a little bat to sync the dev > > tree (your running script) and the cvs repo helps. > > These are all "littly dirty solutions" which were run over the years. > What is so bad if you do > > - check out > - change code > - test > - change code > - test > - commit > > instead of > > - check out > - copy files > - change code > - test > - change code > - test > - copy files > - commit > ??? > > -- > http://www.schlitt.info > http://www.schlitt.info/applications/blog > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > ===== -- Jesus M. Castagnetto (jcastagnetto@yahoo.com) Research: http://metallo.scripps.edu/ Personal: http://www.castagnetto.org/ PEAR stuff: http://pear.php.net/user/jmcastagnetto __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree