[MUD-Dev] Version Control (was: DBs and Events)

[Jon A. Lambert]

On 27 Feb 98 at 20:59, coder at ibm.net wrote:
> On 20/02/98 at 01:47 PM, Vadim Tkachenko <vadimt at 4cs.com> said:
> >coder at ibm.net wrote:
> 
> >CVS announces itself as a wrapper for RCS, as it goes from the docs I
> >managed to read so far, you can keep the repository as a single entity
> >instead of multiple RCS files.
> 
> The following is a commentary on CVS vs PRCS from Stig, one of the
> Xemacs programmers (off-topic I'll admit, except for the fervent
> hope that we all have our source trees under some form of version
> control):
> 

I don't know much about the versioning systems under discussion.  I 
use PVCS from Intersolv which runs on most platforms.  It is 
reasonably priced and has all the functionality I have ever needed.  
It supports releases and source branching.  The API to the product is 
exposed enough so that one could integrate the system into a driver 
and use it to manage mud lib code or any similar scheme should one 
desire.  

I see the mud library code as being somewhat more volatile than 
the driver code and will be storing this internal source code as 
part of my database along with its associate classes and executable
bytecode.  Partly, this is because my bytecode cannot be decompiled
under normal situations (non-debugging).  

I use "versioning" within a class for retaining source code and for 
class attributes.  Of course the source code is just another class 
attribute anyway.  Only the latest version of class attributes are 
cached in memory.  Older versions are retrieved directly from the DB. 
  
--
--/*\ Jon A. Lambert - TychoMUD     Internet:jlsysinc at ix.netcom.com /*\--
--/*\ Mud Server Developer's Page <http://www.netcom.com/~jlsysinc> /*\--
--/*\   "Everything that deceives may be said to enchant" - Plato   /*\--