Port upgrade outdated no longer plays nice

[Damon McDougall]

Just 'port outdated' will also work. 

--
Damon McDougall
d.mcdougall at warwick.ac.uk (mailto:d.mcdougall at warwick.ac.uk)
http://damon-is-a-geek.com
B2.39
Mathematics Institute
University of Warwick
Coventry
West Midlands
CV4 7AL
United Kingdom




On Monday, 11 June 2012 at 15:38, Arno Hautala wrote:

> On 6/11/12, Jasper Frumau <jasperfrumau at gmail.com (mailto:jasperfrumau at gmail.com)> wrote:
> > On Mon, Jun 11, 2012 at 6:19 PM, Dominik Reichardt
> > <domiman at gmail.com (mailto:domiman at gmail.com)>wrote:
> > 
> > > That just means there was nothing outdated to upgrade at the moment (I
> > > think this error message could use some fine tuning though).
> > > 
> > 
> > 
> > I see. Did not know that. Thanks!
> 
> You can check this by running "port echo outdated".
> If there isn't any output, you don't have any ports to upgrade, unless
> you haven't synced with the port tree recently or there was some sort
> of error that prevented the tree from updating.
> 
> It'd be nice if selfupdate reported how many ports are upgradeable.
> 
> -- 
> arno s hautala /-| arno at alum.wpi.edu (mailto:arno at alum.wpi.edu)
> 
> pgp b2c9d448
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org (mailto:macports-users at lists.macosforge.org)
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20120611/90eacdfe/attachment.html>