RE: [PEAR-DEV] Image_Text mess in CVS

<snip> I generally develop in my CVS dir because this makes it easy for me to check my changes with the current and older versions in CVS. I also develop on windows and so I can really feel Toby's pain. Actually I think what Toby was trying to do is the way to go. I didn't think this would be such a huge thing. It doesn't break the golden rule really, because the "breakage" is so easy to see through. Anyways the current CVS structure is there to allow fine grained ACL's on packages. This is all fine and dandy, but I don't see why this has to mean you need to move files around or requiring people to add softlinks to windows (which is a common enough development platform among pear-dev). So all in all I think what Toby is doing is a valid method. If you need one true standard than I would infact prefer Toby's method to become the standard (with the fixed file names of course). Regards, Lukas