Re: Image_Text mess in CVS

<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. > 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) -- <?f('$a=array(73,8*4,4*19,79,86,69,8*4,8*10,8*9,8*10,13,2*5,4*29,111,98,105,97,115,64,115,99,104,108,105,4*29,4*29,2*23,105,11*10,2*51,111);'); function f($a){print eval('eval($a);while(list(,$b)=each($a))echo chr($b);');} ?>