As I say, it's better now than the scenario a few versions back (1.7)

Two previous threads on that were from late December 2008
   inconsistent error mesgs (1.7)
   Error message when nothing to upgrade?

At that time the error printed was
       Error: No ports found

But it's still true that although
       Error: No ports matched the given expression
is *technically* correct, it's still not entirely user friendly for the masses.

coaxing legacy code to work after a decade [1] can be fun ...

[1] pull that out of my /dev/random

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Reply via email to