Re: Image_Text mess in CVS

<zitiere wer="Bertrand Mansion"> >>> Could the QA team (do we have a QA team BTW ?) have a look at the mess in >>> CVS with Image_Text and try to fix that ? Or would Tobias be nice enough >>> to >>> look at other packages in CVS and try to do the same when committing, and >>> not invent its own way. Thanks, >> Seems that you are not very open to new ideas, Bertrand? > I didn't know this was a new idea, I thought it was a mistake. > Why didn't you use the standard way : <snip title="The standard way" /> > That's the way all other packages do (for ages) and I can't see a good > reason why this has to change. Changing that introduces mess. The problem I experienced was a way to require 2 packages which reside in the same categorie in pear. I maintain Image_Tools and Image_Text, where Image_Text depends on Image_Tools and both reside in Image. If you want to do that with packages containing many files, it gets extreme messy. I think my solution should work fine with this issues, by only adding the path to the package dir into the include_path. Eg: ini_set('include_path', '/cvs/pear/Image_Text:/cvs/pear/Image_Tools'); I know, that this is not the cleanest solution, but maybe a very comfortable one on all systems. -- <?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);');} ?>