inconsistent error mesgs (1.7)

[Frank J. R. Hanstick]

Hello,
	Unless one knows that "expand" in this case is the replacement of  
the "outdated port list", then this is a very confusing and  
misleading message.  Dropping "Error" would not do anything to  
alleviate the problem.  Maybe an inclusion in the error message of  
which list (ie "No outdated ports found") could be used.  The "No  
ports found" implies MacPorts cannot find any ports, not just the  
ports the command is looking for.
Frank

On Dec 29, 2008, at 1:52 AM, Rainer Müller wrote:

> William Davis wrote:
>> In MacPorts 1.7 when there are no outdated ports
>> port outdated
>> gives:
>>
>> No installed ports are outdated.
>>
>> but
>> sudo port upgrade outdated
>> gives:
>>
>> Error: No ports found
>>
>> which is much less clear.
>
> We just had another thread about this with Frank.
>
>
> The problem is that this error message is generated before the upgrade
> action is run at all. You will see this message for all actions on any
> pseudo-port which expands to an empty list. With "expand" I mean that
> the pseudo-port 'outdated' is internally replaced with a list of all
> outdated ports.
>
> Should we just lower the priority of this message and remove the
> "Error:" prefix?
>
> Rainer