What is easiest way to identify changes in db/quests?

[Irreverent]

OK, maybe CVS has a cool update-when-new feature...so just looking for help.

Is there a way to quickly identify what .pl or database changes took place?

I could easily drop/create/insert and copy/paste....but due to the complex modifications I have it would be easier to identify and move. Any thoughts or SoL?

[AndMetal]

OK, maybe CVS has a cool update-when-new feature...so just looking for help.

Is there a way to quickly identify what .pl or database changes took place?

I could easily drop/create/insert and copy/paste....but due to the complex modifications I have it would be easier to identify and move. Any thoughts or SoL?

I'm not 100% sure (CVS isn't really my forte), but I think cvs history (http://www.gnulamp.com/cvshistory.html) would do what you're talking about, but I think there would need to be a history file first before that would work.

Then again, maybe cavedude will decide to switch to SVN at some point, which makes it easy :D

What I personally do, since I'm running Linux, is create a quests directory for the server (~/server/quests), then use symbolic links to utilize most of PEQ's quests (~/common/quests/peq_quests (http://eqemuquests.cvs.sourceforge.net/eqemuquests/peq_quests/)) + my changes (~/common/quests/A_work_in_progress). The only hard part is, if you're excluding an entire directory from PEQ & linking back to the PEQ quests in that directory, you'll have to keep any eye out for any new files that are added so you can link those.

[cavedude]

Then again, maybe cavedude will decide to switch to SVN at some point, which makes it easy :D

I probably should. I've been really happy with googlecode SVN for the source, and I even setup one for the PHP editor. The DB and quests should be next.

[John Adams]

I probably should. I've been really happy with googlecode SVN for the source, and I even setup one for the PHP editor. The DB and quests should be next.
YAY!!! Cavedude for Hero '08.