users confusing selfupdate and sync

Jeremy Lavergne jeremy at lavergne.gotdns.org
Thu Oct 15 14:49:03 PDT 2009


>> Is there a way we can better document this or perhaps change the  
>> functionality?
>>
>> We could slip an option into sync so that it does selfupdate unless  
>> you pass it an argument (e.g., sync --portsonly).  This will not  
>> force users to be re-educated and it will provide the benefit of  
>> ensuring people are upgrading correctly.
>
> The best might be to remind users that call "port sync" that "port  
> selfupdate" is the "usual" next step in updating ports. i.e. "port  
> sync" would end by displaying something like
>
>> "Portfiles successfully updated. To upgrade installed ports to  
>> their latest versions, please run port selfupdate."

selfupdate doesn't update anything but update MacPorts itself and the  
ports tree.  If I understood you correctly, they'd then be running  
`port upgrade outdated` which still leaves MacPorts itself not updated.

However, you do bring up an interesting idea I hadn't considered: why  
don't we have a command to do a all-things upgrade?  That is  
`selfupdate` + `upgrade outdated`?



More information about the macports-dev mailing list