On 06/05/2012 05:51 PM, Ted Ross wrote: > On 06/05/2012 06:36 PM, Steven Dake wrote: >> On 06/05/2012 01:05 PM, Ted Ross wrote: >>> I see that many of the definitions in corosync/cpg.h have changed since >>> version 1.x. Is there any documented guidance as to how a user of >>> corosync should most properly migrate to version 2.0, or more >>> specifically, how to conditionally use either 1.x or 2.0? >>> >>> I apologize if this is a duplicate question. I did a quick search of >>> the website and the email archives before asking. >>> >>> Thanks, >>> >>> -Ted >>> >> This is not documented but should be. >> >> I would expect the CPG interface would "just work" without modification. >> We generally have a rule that we don't delete functions but only add >> on. >> >> Regards >> -steve >> > Thanks Steve, > > It looks like we're using deprecated types like "cpg_error_t". I assume > it's safe to just switch over to cs_error_t as that definition is also > in 1.x. > yes cs_* works here for 1.0 and 2.0 Regards -steve > Thanks for the reply, > > -Ted > > > _______________________________________________ > discuss mailing list > discuss@xxxxxxxxxxxx > http://lists.corosync.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
