Sticky branching problem

[Jeff Bowes]

Hi,

I am a newbie to CVS but already have a rather sticky CVS problem to 
solve that seems like it would need several branches.  Here is our 
situation.

We receive some 3rd party open source software that is designed to run 
on Postgres and we need to run it on DB2. However,  we also want to 
maintain a version that will run on Postgres for purposes of 
comparison.  We expect to get reasonably frequent updates from the 
Vendor. Also, some changes to the code will need to be made that are 
carried through on both the Postgres and DB2 versions of code.  (e.g.  
adding some logging, some additional features).

I have read the documentation of branching and documentation on using 
Vendor tags. However, I don't quit know how to put it together to solve 
this problem. I have not been able to find any examples of using 
branching to maintain software versions designed to run on different 
database platforms.

Does anyone have any suggestions on how to set this up?


Thanks very much,


Jeff Bowes