port info reports wrong informations when run with wildcard

[pmq@…]

This bug seems mysterious to me. Here's a short excerpt to display it. Have a look at the "Library Dependencies:" entry.

queinnec@calliope:~$ port info fragrouter
fragrouter 1.6, net/fragrouter (Variants: darwin_powerpc, darwin_i386)
http://www.monkey.org/~dugsong/

Fragrouter is a program for routing network traffic in such a way as to elude most network intrusion detection systems. The attacks implemented correspond to those listed in the Secure Networks ``Insertion, Evasion, and Denial of Service: Eluding Network Intrusion Detection'' paper of January, 1998. See also net/fragroute.

Build Dependencies: libnet, libpcap
Platforms: darwin
Maintainers: pmq@macports.org
queinnec@calliope:~$ port info fragroute*
fragroute 1.2, Revision 1, net/fragroute
http://monkey.org/~dugsong/fragroute/

fragroute intercepts, modifies, and rewrites egress traffic destined for a specified host, implementing most of the attacks described in the Secure Networks {Insertion, Evasion, and Denial of Service:  Eluding Network Intrusion Detection} paper of January 1998.

Library Dependencies: libpcap, libdnet, libevent
Platforms: darwin
Maintainers: nomaintainer@macports.org
fragrouter 1.6, net/fragrouter (Variants: darwin_powerpc, darwin_i386)
http://www.monkey.org/~dugsong/

Fragrouter is a program for routing network traffic in such a way as to elude most network intrusion detection systems. The attacks implemented correspond to those listed in the Secure Networks ``Insertion, Evasion, and Denial of Service: Eluding Network Intrusion Detection'' paper of January, 1998. See also net/fragroute.

Build Dependencies: libnet, libpcap
Library Dependencies: libpcap, libdnet, libevent
Platforms: darwin
Maintainers: pmq@macports.org

As you can see, the port "fragrouter" appears (falsely) to have a library dependency on libpcap, libdnet and libevent, as if the informations for the previous port had been kept. Let me know if you need more info.

[jberry@…]

Works for me on HEAD. This appears to have been fixed by r19992. Thanks for the report.

Fix will be in 1.4.

[jmpp@…]

Included in the release_1_4 branch at branch creation time (r22198).

-jmpp