> Why would that be a shame? We have the chance to rework the API of the > entire package, I want to give ourselves some time to get it right > before we carve anything in stone for an indefinite period of time. > There's no rush, really. You're right. :) I will start the talk with you next week regarding ABI compatibility. I'll give you a rundown of the issues, the potential solutions and we will discuss the usage of libgpiod and the C++ bindings. Jack On Thu, Oct 22, 2020 at 2:56 PM Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > > On Thu, Oct 22, 2020 at 11:47 AM Jack Winch <sunt.un.morcov@xxxxxxxxx> wrote: > > > > [snip] > > > > > > I also don't envision making a libgpiod > > > v2.0 release any earlier than that so we have plenty of time to > > > discuss it and come to the right conclusion. > > > > > > That is also a shame, but at least that gives some time to undertake > > further review of libgpiod v2.0 and potentially make some further > > improvements. What's the time window for this? > > > > Why would that be a shame? We have the chance to rework the API of the > entire package, I want to give ourselves some time to get it right > before we carve anything in stone for an indefinite period of time. > There's no rush, really. > > Bartosz