Re: Image_Text mess in CVS

From: Date: Wed, 12 Nov 2003 13:15:22 +0000
Subject: Re: Image_Text mess in CVS
References: 1 2 3 4 5  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-23526@lists.php.net to get a copy of this message
On Wed, 2003-11-12 at 13:52, Tobias Schlitt wrote: > <zitiere wer="Stig S. Bakken"> > > > Just maintain a second pear install tree for testing: > > > alias peartest="pear -f ~/.peartestrc" > > T=~/peartest > > mkdir $T > > peartest -d bin_dir=$T/bin -d doc_dir=$T/docs -d ext_dir=$T/libexec \ > > -d php_dir=$T/lib/php -d data_dir=$T/data -d test_dir=$T/tests > > > Now you can do "peartest install package.xml" etc. > > That would definitly be a clean solution. But I guess it's unmanagable in > PEAR. CVS is a repository for deleopement. And package.xml is mostly touched > only short befor a release. When I roll releases, I usually change package.xml immediately after the release (or once I start working on the code again), changing the version number to {nextversion}-dev and such. But IMHO it depends on your preference, if you prefer testing in the development tree, there are ways of doing that as well, without breaking current conventions. That's at least the intention behind the "pear run-tests" command. > So, I guess in most cases, the package.xml residing in CVS is not valid for > the code. I would allways have to check package.xml before I can do that. > And that's quite more uncomfortable than handling ln's. > > > If you use "pear run-tests", the current directory is prepended to the > > include_path, so if you follow the convention of having a file structure > > within your package directory, run-tests will do the work for you. > > Most times during developement I do not use pear command (sorry!). I have a > repository, where I get my sources included from (not only those I'm > developing on, but even depending packages, etc.) and a browser / cli script > to test. And I guess, that's the way most developers do. > > Am I wrong? The pear run-tests command is there for your convenience. You can always make your own shell wrappers around php setting include_path and whatnot if that doesn't fit your way of working. I'm just trying to give you some ideas for workarounds you can do on your own rather than arousing the wrath of pear-dev because you stray from the righteous path ;-) - Stig

« previous php.pear.dev (#23526) next »