Re: Image_Text mess in CVS

On Wed, 2003-11-12 at 12:20, Tobias Schlitt wrote: > <zitiere wer="Klaus Guenther"> > > > It's very easy to install the package for testing purposes from the cvs > > directory: > > > $ pear package > > $ pear upgrade -f *.tgz > > This only works, if the package provides a working package.xml at any time > in CVS which is IMHO not given. You would need a second pear installation > for the risk of borking your complete pear installation with developement > state packages. 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. > > CVS structure should merely reflect the package level directory structure, > > not the categories. However, I do understand the problems if you are hunting > > down a bug. The easiest solution is to create a testing file with > > appropriate paths... or modify a local copy of the unit tests ;-) > > Sorry, but I really dislike that. When I start debugging a foreign package > (because I have to use it right now) I do not want to spend time on all > those things before I can really start the doing. > > And has anyone a solution for the inclusion of 2 packages residing in the > same categorie? (Except this crappy "include all files of the package by > hand" thing) 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. - Stig