bug: case sensitive port names in boolean expressions

[mojca (Mojca Miklavec)]

The following doesn't work properly:

> sudo port upgrade outdated and not filezilla
--->  Computing dependencies for FileZilla
...

[Ionic (Mihai Moldovan)]

Also happens the other way around - in case that a port has been renamed in a case-only way and a boolean expression is added (correctly-cased, incidentally), the implicit part is buggy.

See #55241 for a more detailed description.

Concise description: mediainfo was renamed to MediaInfo, port outdated and port echo outdated both listed it, but port upgrade outdated and not GitX or port echo outdated and not GitX would not upgrade/list it.

Interesting side fact: port outdated and not GitX does list the affected mediainfo port, though that may be "questionable usage of boolean expressions" (since outdated in this context is a command).

[neverpanic (Clemens Lang)]

Can reproduce with XviD installed and the commands

$> port installed installed and not XviD
$> port installed installed and not xvid

[ryandesign (Ryan Carsten Schmidt)]

Does anybody know where in MacPorts base these Boolean expressions are handled? Trying to search base for "and" or "or" has been pretty futile.

[raimue (Rainer Müller)]

The code is in the port client. You are looking for andExpr and orExpr, which then use the opIntersection and opComplement operations on the port list. ​https://github.com/macports/macports-base/blob/ec4ae2dc3d0f736c3c247fcf83e33f87223fad2f/src/port/port.tcl#L1106

[jmroot (Joshua Root)]

Ticket retargeted after milestone closed

[jmroot (Joshua Root)]

Ticket retargeted after milestone closed

[jmroot (Joshua Root)]

In bd02a2fba3ec2d10972bf02512e999a1662f92d3/macports-base (master):

Compare normalised port names in boolean ops

Fixes: #50518