[MacPorts] #50388: py-bob @2.0.7 New release

[MacPorts]

#50388: py-bob @2.0.7 New release
--------------------------------+----------------------
  Reporter:  tiagofrepereira@…  |      Owner:  devans@…
      Type:  update             |     Status:  closed
  Priority:  Normal             |  Milestone:
 Component:  ports              |    Version:
Resolution:  fixed              |   Keywords:
      Port:  py-bob             |
--------------------------------+----------------------
Changes (by devans@…):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 OK, André, I've committed the updates in r144969 and the ports are in the
 process of rebuilding on our buildbots.  Looks like things are going well
 but issues remain on 10.8, 10.6 and presumeably 10.7.  I'll update the
 various tickets after the builds complete.

 Concerning MacPorts' rebuild policy, everything you say is correct.  I
 believe the decision to require the port maintainer to decide when to
 rebuild a port stems from a desire to minimize the number of rebuilds to
 just those that are absolutely necessary.  Until rather recently, doing a
 rebuild meant that every MacPorts user would have to do the rebuild on his
 own machine.  This is still the case for 10.11 since we don't have a
 buildbot for that version commissioned as yet.  The problem is now
 mitigated to some degree by our ability to provide prebuilt binaries for
 the various ports where licensing allows but we do receive reports
 periodically concerning the need to constantly rebuild.

 Experience has shown, that, more often than not, the fact that a port has
 been updated does not automatically mean that its dependents need to be
 rebuilt.  This is generally necessary only when there are ABI/API changes
 or when dependencies themselves change.  In addition, you need to consider
 that we are dealing with a great number
 of ports from a great number of upstream developers who, by large, do not
 agree on when versioning changes indicate the need for a rebuild.  Some
 ports almost never need their dependencies updated on version change
 (glib2 for instance) while others change their binary versioning on every
 minor update (poppler).

 Thus, rather than trying to come up with an intricate algorithm for
 automating this problem (and probably getting it wrong), the current
 policy is for each port's maintainer to understand his port and the other
 ports that depend upon it and manually force a rebuild when necessary by
 incrementing the revision number.

 I should point out that the port program itself maintains a local database
 of binary versions on a file by file basis and checks for binary
 mismatches at the end each build.  The default behavior is to force a
 rebuild if a mismatch exists.  Of course, this is not always the correct
 action and the behavior can be configured to just report if desired.

 Hope this helps clarify the issue for you.  If not, please feel free to
 contact me directly or to raise a discussion on the developer's email
 list.

 Thanks for your update. Sorry it took so long to complete.

 Dave

-- 
Ticket URL: <https://trac.macports.org/ticket/50388#comment:12>
MacPorts <https://www.macports.org/>
Ports system for OS X