Closed mstaflex closed 2 years ago
Maybe it would be a good idea to not push directly to master, which indicates a stable state version, but do changes like that on either development branches, or feature branches altogether? :)
Hi, please update your sysrepo version, they have changed their API. We are generally tracking the devel
branch of sysrepo.
https://github.com/sysrepo/sysrepo/blob/devel/src/sysrepo_types.h#L354
I've updated the required version of sysrepo, I should have done that with the API changes, oh well.
Ah ok, thx for coming back to quickly.. will try that out :)
From the outside perspective that is a bit obscure that the master here tracks devel on sysrepo ;)
I would have to implement the API changes anyway at some point. Quite a lot of features are implemented in sysrepo-cpp already, but I still consider them a work in progress, so I think that tracking the latest sysrepo is fine. As of now, sysrepo/devel equals sysrepo/master.
Thanks for catching the version, however, I didn't realize that I should increase it!
And to provide a bit more of an additional context to what @syyyr has already said -- we're writing these bindings and porting our apps to them at the same time. We still keep changing the APIs a little bit, so there's no API or ABI compatibility just yet. We also bump into some bugs of upstream sysrepo every now and then, so in general it's better for us to follow the upstream development closely -- hence we're targeting their devel
branches. There are, however, some technical reasons in our CI/CD stack why we prefer to call our branches master
and not devel
.
When compiling master on https://github.com/sysrepo/sysrepo-cpp/commit/0f6791ec2102d2761c2deff67954ee6eed1cff43 I run into enum conflicts that are picked up by your static asserts:
Comparing this with
sysrepo
Version 2.0.53
insrc/sysrepo_types.h
(https://github.com/sysrepo/sysrepo/blob/39bc5adb98026af355febcca5abf27d44ebf6f10/src/sysrepo_types.h#L345) the former values were actually correct.Only
was missing from the list.