port -u upgrade outdated

[Ryan Schmidt]

On Oct 4, 2007, at 21:57, Thomas De Contes wrote:

> Le 5 oct. 07 à 00:22, Ryan Schmidt a écrit :
>
>> On Oct 4, 2007, at 15:44, Emmanuel Hainry wrote:
>>
>>>> port -u upgrade anything
>>>> is equvalent to
>>>> port upgrade anything
>>>> port uninstall inactive
>>>> am I right ?
>>
>> No,
>
> ah, well,
> port -u uninstall anything
> is equvalent to
> port uninstall anything
> ?
> if not, what is different ?

If you only have one version of foo installed, then "port uninstall  
foo" is the same as "port -u uninstall foo".

If you have several versions of foo instaled, for example foo 1.2.1_0  
and foo 1.2.1_1 and foo 1.2.3_0, then "port uninstall foo" will do  
nothing and print an error message that it does not know which  
version of foo you would like to uninstall, and "port uninstall foo  
@1.2.1_1" will uninstall only foo 1.2.1_1 and leave the other two  
installed, and "port -u uninstall foo @1.2.1_1" will I believe  
uninstall all three foos. I don't feel like testing this right now  
but you're welcome to. Also I'm not sure what "port -u uninstall foo"  
would do -- would it error out and make you select which foo, or  
would it just uninstall all 3? I don't know.

>> "port -u upgrade foo" uninstalls inactive versions of foo before  
>> activating the new version of foo. It does not affect ports other  
>> than foo. "port uninstall inactive" uninstalls all inactive ports  
>> (whether those ports are foo or bar or baz or whatever).
>
> ok, so if i find how to do
> port -u upgrade outdated
> i don't need to activate all first :-)
>
> well, if i don't forget anything,
> what i need is to tell "port" that i want to force the "uninstall",  
> but not to force the rebuild of all dependencies
> but -f forces both
>
>
>>>> so,
>>>>
>>>> port -u upgrade outdated
>>>> doesn't works because it needs -f to uninstall
>>
>> Right, if ports depend on the ports being upgraded, then -f is  
>> needed so MacPorts won't complain.
>>
>>>> port -fu upgrade outdated
>>>> is not fine, because with upgrade it rebuilds all dependencies,  
>>>> so it needs
>>>> -n to build only outdated
>>
>> Right.
>>
>>>> port -nfu upgrade outdated
>>>> doesn't works because the upgrade is not done in the right  
>>>> order ... :-( !
>>
>> I believe that's right. I'm not sure what order the upgrades are  
>> done in, but I'm not convinced it's the right order.
>
> as i said, when i tried that i got an error ... so there is sth wrong

It could mean there's a bug in the new version of whatever port was  
being updated. It doesn't necessarily mean it was a dependency problem.

>> Consider that apache2 depends on apr and apr-util, and that apr- 
>> util also depends on apr. "port outdated" would print these in the  
>> following order: apache2, apr, apr-util. So if you upgrade these  
>> in alphabetical order, apache2 will be upgraded first, and it will  
>> build against your old version of apr and apr-util. Then apr will  
>> be upgrated, and then apr-util will be upgrated and will link  
>> against the new version of apr. If the changes in apr and apr-util  
>> are minor (binary compatible with the previous release), this  
>> won't be a problem, but if the ABI changed, then apache2 will be  
>> broken after apr and apr-util are upgraded. Also, it may be a  
>> problem that apache2 uses apr-util but apache2 and apr-util have  
>> been built against different versions of apr.
>
> well, if apr and apr-util are outdated, but not apache2, we need to  
> rebuild apache2 because it depends on ports which are upgrated, is  
> it right ?
> does "port upgrade outdated" do it ??
> if yes and no, "port -u upgrade outdated" is right to do not  
> uninstall by default, since it may cause stuff to stop working

If the ABI has not changed in the new version of apr or apr-util,  
then no, apache2 probably does not need to be rebuilt. However, if  
the ABI did change, then yes, anything that depends on apr and apr- 
util should be rebuilt, and no, port upgrade outdated does not do it  
for you. Hence, occasional problems such as the one in the problem  
hotlist after gettext was updated from 0.14.x to 0.15.x:

http://trac.macosforge.org/projects/macports/wiki/ 
ProblemHotlist#a2.Aportfailedtobuildupgradeorrunwithamessagereferringtol 
ibintl.3.dylib

> so, it would be good to make an option to port which allow us to  
> force to rebuid *dependents* of ports which are upgrated, but not  
> *dependencies* of them
> so that, "port -u upgrade outdated" should be able to uninstall  
> without -f , is it right ? :-)

It would be useful not to need to "force" something that is a rather  
regular operation, yes. I'm not sure of the correct way to implement  
it. I haven't given it much thought.

> ps :
> "man port" says "outdated: *installed* ports that are out of date ..."
> but it seems that it is *active* ports, not installed ones

I agree with you:

$ port installed wxWidgets
The following ports are currently installed:
   wxWidgets @2.8.4_2+darwin_8 (active)
$ port outdated
The following installed ports are outdated:
p5-compress-zlib               2.006_0 < 2.007_0
wxWidgets                      2.8.4_2 < 2.8.6_1
$ sudo port deactivate wxWidgets
--->  Deactivating wxWidgets
$ port installed wxWidgets
The following ports are currently installed:
   wxWidgets @2.8.4_2+darwin_8
$ port outdated
The following installed ports are outdated:
p5-compress-zlib               2.006_0 < 2.007_0
$

So either we have a bug in the manpage, or we have a bug in base. You  
may wish to submit a ticket in Trac for this problem.