Re: php + cvs

Bostjan Skufca @ domenca.si wrote:

a. It would create a posibility to run application directly from CVS if http server would have access to it

doeos anyone else think this is silly? besides which this is webdevelopment, the http server's config/paths etc matter ... so how do the files inside the CVS repository know which server is using them? also have you ever looked at the contents of a repository? its full of *,v files which are not usuable as-is. direct access to the files in your CVS repository is a BAD IDEA... unless of course you are a certified wizard in which case I'll just shut up ;-) instead write an automation script to update/export/roll-out your application.... actually thinking about it a friend of mine setup CVS once so that checking in automatically caused a test-server to be updated to the latest version... (can't remember how he did it)... that sounds more like what you want.

b. details :))

yeah ;-)

On Tuesday 31 May 2005 18:06, Jochem Maas wrote:

Bostjan Skufca @ domenca.com wrote:

Hello, is it possible to mount CVS/SVN repository as filesystem?

a. why would you want to? (the whole idea is that you _dont_ edit files directly in the repository) b. this is a php mailinglist not a cvs mailinglist. ;-)

regards, Bostjan On Tuesday 31 May 2005 15:46, M. Sokolewicz wrote:

Marcus Bointon wrote:

On 31 May 2005, at 09:58, Jochem Maas wrote:

Also I hear lots of good things about subversion (SVN), which is a newer alternative for version control - some even say its better.

I can definitely vouch for Subversion. I'm using it for all my PHP stuff. I'd not used cvs a great deal, but I'd always found it awkward and svn is certainly easier. The home page is here: http://subversion.tigris.org/ The documentation (an online O'Reilly book) is excellent. It's pretty easy to learn (shares most basic commands with cvs), and there are many helper apps to work with it, not least TortoiseSVN which looks and works just like TortoiseCVS. I'm on OSX with OpenBSD and Linux servers and it's been easy to get it working over HTTPS. There are some OSX clients (notably svnx), but I find that once you figure out the commands, the command line interface is very easy to work with. Consensus seems to be that if you're just starting out in version control, go straight to svn so you can skip all the reasons that made them want an upgrade from cvs! Marcus

another CVS/SVN helper-application is smartSVN (or smartCVS for CVS): http://www.smartsvn.com/ (http://www.smartcvs.com/ for CVS). Those applications are really nice, personally I find that they are far easier to handle than tortoiseCVS(/SVN)