ImageMagick @6.9.11-60_3 seems to be configured for unused, maybe unusable software

[ballapete (Peter "Pete" Dyballa)]

There are two configure options that do not seem to fit into the Mac world: --with-dps and not --without-raqm. Display PostScript was developed on NeXT, but never used in Mac OS X or macOS, its successor(s). So its activation makes no sense. Similarly Raqm, which seems to be a product for MS Windows. Besides both softwares are not (yet) supported by MacPorts. It would accelerate building ImageMagick when it would be configured --without-dps --without-raqm.

[ballapete (Peter "Pete" Dyballa)]

Similarly FLIF, the Free Lossless Image Format, can be sorted out by using --without-flif. It's also not supported by MacPorts. And if installed by other means, would port or configure be able to find it?

[ryandesign (Ryan Carsten Schmidt)]

--with-dps was added in [cea379c3084322297ecad7314f3db9d8ddd99366/macports-ports] as part of the fix for #847 but the ticket does not explain that change specifically and it was 19 years ago which predates my involvement with MacPorts so who knows why that was done at this point.

As to raqm and flif, I suppose I didn't add the configure arguments because I didn't realize they existed. You're right that we should specify any --without- or --disable- flags that we can when that would prevent the use of a library that we don't want to use, even if that library is not yet in MacPorts. For libraries that are not macOS-compatible, it's less urgent since any check for such a library would fail on macOS.