RE: [PHP] CVS style project system

I know you don't want to hear someone say use cvs so... Use viewcvs[1], or write your own version of it. You can put a database behind it, add descriptions to projects and/or folders to your database, whatever you want on top of cvs. You can even use cvsgrab[2] to download a repository from a viewcvs site. There is also cvsweb[3], if you think perl is better than python. If you need to significantly extend the functionality of these possible solutions and you still want to hack out some PHP code then use these as a base for designing whatever you are looking for. As a side note, cvsgraph[4] integrates nicely with viewcvs, and if you do use viewcvs check out the querycvs script. The points I am trying to impress are: 1.) Writing your own version of cvs in PHP is a bigger deal than you likely realize. Even if you do not need every single possible feature of cvs your project will probably grow and you may some day. 2.) The rcs format does a good job of maintaining version control and if you use cvs you get all of its stability, future improvements, etc. 3.) There is a long history behind cvs. It has accumulated a large amount of supporting applications, helper scripts, mailing lists (of which I am on btw), etc. In short an entire community. It would be better for us all if you would join in and help yourself. 4.) Short of using webdav[5] as well as basic HTTP it is a poor usability decision to design a file based revision control system with its only interface being via HTTP. What if people want to download entire directories, etc. You can make direct cvs access an afterthought, but still a possibility. 5.) I am of the camp that thinks storing entire files in a database is a bad thing. Think of your filesystem as a database optimized for storing files. class new_wheel extends wheel > class new_wheel Regards, Adam Ideally how could i set this up, so it can force the users to downlod the latest copy before uploading a newer version, or once a new copy is uploaded it is emailed ?