libavif-devel: New port for debug only

[Dave-Allured]

Description

• New debug port for libavif @ 1.4.2.
• For debugging legacy builds only. Not for public use.

Type(s)

• enhancement

Tested on

CI only.

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• checked your Portfile with port lint?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?
• checked that the Portfile's most important variants haven't been broken?

[reneeotten]

I am personally not in favor of adding -devel ports just for debugging legacy systems. Again, if you want to do that type of work you presumably have an older OS and can do so locally.

[Dave-Allured]

I am personally not in favor of adding -devel ports just for debugging legacy systems.

Yes I do understand your viewpoint. That does seem like a nuisance.

Again, if you want to do that type of work you presumably have an older OS and can do so locally.

I wish that were so, but no. I do not have local access to any macs older than Sequoia. My only access to legacy systems is through MacPorts builders. From my point of view, the builders seem well suited for controlled experimentation.

My general reason for legacy work is because I think it improves MacPorts overall. Lately I have been more interested in legacy problems in very popular ports, potentially affecting many users. libavif is one such because it is a dependency of some other popular A/V applications.

I think that a temporary debug port is better than multiple legacy experiments on the live port, with the risk of disturbing other users. Will this be acceptable? If necessary, I could agree to delete the debug port after the debugging problem is finished.

[Dave-Allured]

Ready for merge. However, wait until MacPorts builders come back on line.