port check netpbm does not look to work

[lucbouge (Luc Bougé)]

I have run sudo port check installed on my extended MacPorts repository (more than 500 packages).

It is all fine but, alone among the 500+ packages, libnetpbm and netpbm do not seem to register that they have been checked.

$ port -v
MacPorts 2.4.2
$ sudo port check installed
--->  Computing dependencies for libnetpbm
--->  Computing dependencies for netpbm
$ sudo port check installed
--->  Computing dependencies for libnetpbm
--->  Computing dependencies for netpbm
$ sudo port check installed
--->  Computing dependencies for libnetpbm
--->  Computing dependencies for netpbm

Is it normal?

Best regards,

Luc.

[lucbouge (Luc Bougé)]

(Sorry for mis-formatting.)

I have run sudo port check installed on my extended MacPorts repository (more than 500 packages).

It is all fine but, alone among the 500+ packages, libnetpbm and netpbm do not seem to remember that they have been checked.

$ sudo port -v 
MacPorts 2.4.2 

$ sudo port check installed 
---> Computing dependencies for libnetpbm 
---> Computing dependencies for netpbm 

$ sudo port check installed 
---> Computing dependencies for libnetpbm 
---> Computing dependencies for netpbm 

$ sudo port check installed
---> Computing dependencies for libnetpbm 
---> Computing dependencies for netpbm

$ sudo port info netpbm
netpbm @10.80.01 (graphics)
Sub-ports:            libnetpbm
Variants:             universal, [+]x11

$ sudo port info libnetpbm
libnetpbm @10.80.01 (graphics)
Variants:             universal

Is it normal?

Best regards,

Luc.

[ryandesign (Ryan Carsten Schmidt)]

sudo port check X does not check port X in any meaningful way. Its only purpose is to verify whether the checksums of the distfiles of port X match. This is because MacPorts allows you to abbreviate any commands so long as they remain unique. So sudo port check is an acceptable abbreviation of sudo port checksum.

netpbm and libnetpbm do not have any distfiles so there are no checksums to verify.

If you want to run the developer testsuite of port X, you can use sudo port test X. You probably want to use the debug or verbose flags so that you can see the results of running the tests, e.g. sudo port -d test X. Note that running the tests will first rebuild the port from source, which can take time and disk space. To reclaim the disk space after running the tests, run sudo port clean X. Also note that not all ports have tests enabled, and that even those that do might not have passing testsuites.

If running the testsuite is not what you were looking for, let us know what you were expecting sudo port check to do.