[MacPorts] #26585: Intelligent upgrade

[MacPorts]

#26585: Intelligent upgrade
---------------------------------+------------------------------------------
 Reporter:  tommyd@…             |       Owner:  macports-tickets@…                   
     Type:  enhancement          |      Status:  new                                  
 Priority:  Normal               |   Milestone:                                       
Component:  base                 |     Version:  1.9.1                                
 Keywords:                       |        Port:  p5-io-compress-zlib                  
---------------------------------+------------------------------------------

Comment(by macports@…):

 Replying to [comment:3 ryandesign@…]:
 > Replying to [comment:1 macports@…]:
 > > Hey, if we are going to make upgrade intelligent, maybe we should make
 it really smart and have it build libraries BEFORE the things that depend
 on them rather than AFTER. That way, when something happens like OpenSSL
 is updated, a port upgrade would build it first rather than last. That'd
 save the time of the devs who are busy bumping revs on everything to clean
 that mess, AND it would save the time of the users for who the upgrade
 built OpenSSL AFTER all the ports with bumped revs who now have to upgrade
 --force a whole pile of basic stuff. Cause, you know it sucks when that
 port upgrade fails because it upgraded OpenSSL AFTER subversion and then
 hits a port that wants to use the now-broken subversion to fetch the files
 to build the current port being upgraded.
 >
 > MacPorts already does handle upgrading dependencies first, in the
 correct order. I'm unclear how you arrived at the situation you describe,
 unless you encountered a port that did not properly declare its
 dependencies.
 >
 > > Also, when we are in this situation, it'd be nice if macports had a
 function to check the version of libs linked against my installed ports
 and rebuild as necessary to resolve those with missing versions. That
 would be much better than posted a script to the mailing list that is
 written for one specific library and version in question and has an
 assumed prefix hardcoded. I know a generic and reusable solution is really
 pushing it but in the long run it's a win.
 >
 > Contributions are welcome.

 I have attached a file which is the log of the port upgrade in question.
 Notice the order in which subversion and openssl are built. Subversion
 comes BEFORE OpenSSL, as does serf, so both had to be rebuilt to get
 subversion working. Both those ports list openssl as a dependency so why
 does macports build them in the wrong order?

-- 
Ticket URL: <https://trac.macports.org/ticket/26585#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS