Am Donnerstag, dem 09.03.2023 um 14:24 +0100 schrieb Ladislav Michl:
> On Thu, Mar 09, 2023 at 10:38:15AM +0100, Alexander Dahl wrote:
> > Hei hei,
> > 
> > Am Thu, Mar 09, 2023 at 10:29:06AM +0100 schrieb Michael Olbrich:
> > > On Thu, Mar 09, 2023 at 10:08:50AM +0100, Juergen Borleis wrote:
> > > > With change a08638d93d19624cf3c20d033ea8f61b96c43408
> > > >   "libmodbus: version bump 2.0.4 -> 3.0.8"
> > > > libmodbus changed from 2.x.x to 3.0.x version like libmodbus3 did.
> > > > 
> > > > And with change a76b31d5b637bc89ca26e7fa81503cbc7632b666
> > > >   "libmodbus3: version bump 3.0.6 -> 3.1.4"
> > > > libmodbus3 switched to the recent to 3.1.x version.
> > > 
> > > Hmmm, it feels like there were supposed to be for two packages, one for
> > > version 2.x and one for 3.x, at least it started that way.
> > > I don't really know anything about libmodbus. Are the two versions
> > > incompatible?
> > 
> > Yes, 3.0.x and 3.1.x have incompatible APIs and probably ABIs.
> > 3.0.x has .so version 5 and 3.1.x has .so version 6, at least to my
> > notes and the code trying to distinguish this.
> > 
> > Greets
> > Alex
> > 
> > > 
> > > Ladislav, you touched it last, you did the "2.0.4 -> 3.0.8". Do you have
> > > any insight here?
> 
> As Alex pointed out above, 2.0.x has incompatible API and was last
> touched 12 years ago. I pretty much doubt anything sane currently depends
> on it and the truth is I overlooked libmodbus3 while doing update.

It is even more worse: 2.x.x API != 3.0.x API != 3.1.x API 🙂

jb

-- 
Pengutronix e.K.                       | Juergen Borleis             |
Steuerwalder Str. 21                   | https://www.pengutronix.de/ |
31137 Hildesheim, Germany              | Phone: +49-5121-206917-128  |
Amtsgericht Hildesheim, HRA 2686       | Fax:   +49-5121-206917-9    |



Reply via email to