Re: Image_Text mess in CVS

> > If we come up with correct ways for handling files in CVS / on > > harddisk and about the filenames I'd volunteer to have a look at the > > current package to try to help solve some inconsistencies with the > > where possible. (Background: You can't move / rename files in CVS > > without loosing CVS-history for that file - so renaming / moving > > should be done directly on the server via SSH). > > That's not the point. The CVS structure doesn't have to reflect your test > environment. First you test your code then you commit the changes to CVS. > You shouldn't test your code directly in CVS unless you want to add mess to > your repository. The proposed changes are wrong. It's very easy to install the package for testing purposes from the cvs directory: $ pear package $ pear upgrade -f *.tgz 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 ;-) Klaus