Re: Image_Text mess in CVS

<zitiere wer="Stig S. Bakken"> > 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. I can imagine that most of the old-school pear devs have their own, working solution for the issue. And I believe, that there are many workarounds to handle the issue we are talking about. But don't you think, most of the arguments on this huge thread are in the way of "I have my developement environment running, so do not come up and try to change my consuetudes". What I was testing on the CVS tree was my prefferred solution and far away from that only a proof of concept. The changes I did would definitly make work on pear packages (for maintainers, documentors, patchers and even users) a big piece more comfortable and would not disturb anyone who likes copiing files around and using ln to solve things. I do not want to force anyone to do things my way, but I hope that there is enough community spirit to think twice about a solution and it's benefits, befor it is rejected. >> 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 > ;-) Do you really think, I "stray from the righteous path"? The CVS issue is definitly not the biggest one in pears problems. But it exists and it makes life difficult for many developers. About pear run-test, I can say, that I never used it. During developement I want to have either a complide IDE with debugging features or a var_dump() in my browser window. Beside that, commandline testing is not possible in many cases, as image manipulation. Don't get me wrong. The intention of my test on the pear cvs was just a proof of concept for my personal use. But I guess that there are many developers, who barf about that problems. -- <?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);');} ?>