Re: crypt_rc4 cvs

Lukas Smith wrote:

Dave Mertens wrote:

Lukas Smith wrote:

I was recently on the train and needed a version of crypt_rc4. so i used the one from CVS only to find it is now php5 only. looking at the source it seems this work will become the next major version of crypt_rc4. so it seems that no BC break was intended. however i would suggest to develop the new major version in a new cvs folder according new name (which would be Crypt_RC4v2 .. yeah i know its ugly :-( ... note that the RC is supposed to be all capitals since its an acronym however the v is supposed to be lower case )

First, the 'original' php4 code is saved under the brance php4, which would allow me to fix previous version of Crypt_RC4.

Oh .. forgot to look deep enough. sorry for the false alarm.

No problem. It's not a common place to look. On the other hand, it's obvious that you'll find the last version in CVS ;-)

generally i dont think that using branches for this is the optimal way to go. as for version history i guess setting a tag when the split is made should be sufficient. But that is just personal preferences and obviously no standard.

Well, I'm pretty sure I am not the only programmer which has multiple major version of a package. Maybe it's time to setup a bunch a guidelines? My toughs about both methods CVS branching - Pro's: - Using CVS as it's designed. Working on multiple version of a project - Keeping full history of all files CVS branching Con's: - deeper knowlegde of CVS required New directory Pro's: - Very clear to end-users and and the more sleepy developers ;-) New directory Con's: - 'Wildgrow' of directories - Loss of file history (unless an CVS administrator moves (copies) the actual files on the CVS server itself) - I not fully into the cvs karma's, but this would also mean that all pear developer must have right to create new directories. Because it's now required to propose new packages (and their directory) using pepr, you might expect some sort connectie between pepr and cvs to prevent unauthorised package creation. It's might be possible that some enabled my integration mode.. Regards, Dave Mertens