Recent content by Mthales

For more details check this out: http://www.network-theory.co.uk/docs/cvsmanual/cvsignore.html "I may not have gone where I intended to go, but I think I have ended up where I needed to be." --- Douglas Adams

What cvs version and client are you using? For an example TortoiseCVS will by default ignore files and folders that match the following cases: core RCSLOG tags TAGS RCS SCCS .make.state .nse_depinfo #* .#* cvslog.* ,* CVS CVS.adm .del-* *.a *.olb *.o *.obj *.so *.Z *~ *.old *.elc *.ln *.bak...

The basic procedure for moving cvs repositories holds true for any server architecture and it goes something like this: 1 - Install and configure cvs on the new server. 2 - Copy the repositories onto the new server. 3 - Check the configuration for the repositories on the new server. 4 - Get...

While that is basically possible you probably want to look at using something more flexible like ViewVC to display cvs controlled content through a web-browser. http://www.viewvc.org/ "I may not have gone where I intended to go, but I think I have ended up where I needed to be." --- Douglas...

I think you may be misunderstanding what the checkout list actually does. It's not for when you check out the CVSROOT into a sandbox so no the files you list should not be appearing in the CVS folder with the meta data. The checkout list works when you commit changes to the files in CVSROOT. If...

Hi, Check this out CVS Suite 2008 x64 (HPUX, Solaris, SuSE/SLES9) from the people who support CVSNT. "I may not have gone where I intended to go, but I think I have ended up where I needed to be." --- Douglas Adams

This doesn't seem to be a question - so it's hard to know what to offer as help or advice. But can I suggest you do a web search for information about tags and maybe branches as these are ways of keeping a track of different sets of files (each at their own version numbers) that fit together to...

There is quite a bit of information on the basics of this on the web - you could start by reading pages like this: http://www.pragmaticautomation.com/cgi-bin/pragauto.cgi/Monitor/LettingCVSPullTheTrigger.rdoc/style/print I myself have a post commit call to a script that does some simple...

I'm glad you found the answer yourself but yes it's down to the hosting os and not restricted by CVS. "I may not have gone where I intended to go, but I think I have ended up where I needed to be." --- Douglas Adams

Well that's the bit is really bespoke - dependent on how you need to change stuff about to fit from your sandbox into your working area. It could be as simple as "cp -ru * /working_dir/ " or it could get really complex. "I may not have gone where I intended to go, but I think I have ended up...

They are very specific to the web server directory and repository structures that we use so they'd not be much good to you. I don't want to teach you to suck eggs but very basically they go something like this: #!/bin/bash cd <the landing area I've already set up as a sandbox - so I don't...

I don't want to be funny but that's not really appropriate for this forum. However I'm sure if you have a go at something simple (there are loads of good starter tutorials on the web) and then ask questions in (somewhere like) this site's Unix scripting forum then someone, maybe even me, will...

The way you plan to do this - with a landing area - sounds very sensible and very script-able to me. You'll be able to have the script do a CVS update to get the latest versions into this area and then check them against the working files and copy the changes it recognizes the right locations...

you can do a merge from the tagged (or probably branched) version back to the trunk to keep your changes for people working on the trunk. Do a quick web search on the merge keyword and you should find all the instructions you need. "I may not have gone where I intended to go, but I think I...

It's saying that you have this file checked out to the version 1.5 - so in your sandbox you need to do an update to the BRANCH TAG that you want to be working on. Then you'll really be working on the branch and able to do the commit. I hope you'd worked this out by now - but if not I hope that...