The immediate need is to put out a bugfix release. If we bump the soname then it won't be a drop-in replacement, and Hugin will need to be rebuilt for all platforms etc..
These bugs are not relevant to Hugin users, but they are still security issues, so Linux distros will be looking to update their pano13 packages as soon as we do a release. It would be nice to have this be a minimal change without bumping the soname. I'm not confident I can do this change that keeps the ABI intact, so looking for help here. -- Bruno On Sun, 30 Jul 2023, 13:13 Andreas Metzler wrote: > On 2023-07-22 Andreas Metzler wrote: > [...] > > I am not in favour of that, you'd still break the functional (but > > unused, yeah) interface. Also WriteScript/WriteResults changes would > > need to be reverted to keep the ABI unchanged. > > > Imho there is a simple way to do this cleanly and no need to try to be > > clever about it. > > Hello, > > Would it be possible to find/list the externally "useful" functions? > If that were the case we could change the buildsystem to only export > these in the library ABI and would not have ABI breakage on further > internal cleanups like this one. > > cu Andreas > -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/CAJV99ZhOLe7a8njBViqQ656HCS1CDyWb4p0sNLRHXos5TWDTjw%40mail.gmail.com.
