You were comparing 1.1.10 to 1.1.3. I'm pretty sure those changes weren't in the last couple releases. So I'll assume that if it broke blender, we would have noticed months ago.
On Apr 23, 2013, at 10:41 AM, Richard Shaw wrote: > On Tue, Apr 23, 2013 at 12:14 PM, Larry Gritz <[email protected]> wrote: > Thanks, that's an interesting report. > > Yeah, I've found it to be very helpful on a number of packages, especially > ones that do not manage API/ABI compatibility, like collada. I can use this > tool to let me know if I need to request rebuilds of dependents. > > > I think that these are all harmless, though. Most are cases of new API calls > being added. In one case, a parameter was renamed (truly of no consequence), > and in two cases a default argument was turned into no longer a default. > > In all cases, old apps that switch to link against the new library should be > fine without recompilation. It's possible, in the case of the changing > default argument, that if you recompile the app source and you happened to > rely on that default argument, you'll need to patch it to pass the argument. > This change was not intentional. But I'm pretty sure it happened several > releases ago, not in the latest couple updates, so I'm tempted to not worry > about it unless you think it's important to change it again to restore the > default. > > I'll be more careful in the future about not changing default parameter > values in release branches, I didn't really mean to do that. > > No problem. I still think the only direct dependency in Fedora is Blender but > I'll check just to be sure. > > Thanks, > Richard -- Larry Gritz [email protected]
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
