#50388: py-bob @2.0.7 New release --------------------------------+---------------------- Reporter: tiagofrepereira@… | Owner: devans@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-bob | --------------------------------+---------------------- Comment (by andre.dos.anjos@…): Hello Dave, Indeed, this commit has changed the API version for bob.core on Nov 28th last year: https://github.com/bioidiap/bob.core/commit/57dd5a01c451c7c90d51a3f0c77138f3... Version 2.0.5 of bob.core was shipped with API 0x200 (Nov. 26th). Version 2.0.6 was shipped with API 0x201. According to our own rules, we should have shipped version bob.core-2.1.0 instead of 2.0.6. We'll fix it. Meanwhile, I'm not sure I understand the issue: if package B depends on package A and package A is version upgraded, shouldn't package B be re- compiled? How to mark API changes that may require recompilation of dependencies? Best, A -- Ticket URL: <https://trac.macports.org/ticket/50388#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X