Re: Image_Text mess in CVS
| From: | Stefan Neufeind | Date: | Wed, 12 Nov 2003 16:41:03 +0000 |
| Subject: | Re: Image_Text mess in CVS | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23543@lists.php.net to get a copy of this message | ||
On 12 Nov 2003 at 11:18, Bertrand Mansion wrote:
> <stefan@neufeind.net> wrote :
>
> > 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.
Please also have a look at Archive_Tar:
http://cvs.php.net/cvs.php/pear/Archive_Tar?login=2
Seems like Toby didn't invent the wheel again - there it's already
done the same way (having Archive_Tar/Archive/Tar.php etc.).
I don't see the problems when using a directory/file-layout like this
in CVS ... and as has been mentioned on the list there are even a few
good sides of doing it this way.
Stefan