math/z3: Update 4.15.3 => 4.15.4

[alven]

Summary

Changelogs:

• https://github.com/Z3Prover/z3/blob/master/RELEASE_NOTES.md#version-4154
• https://github.com/Z3Prover/z3/compare/z3-4.15.3...z3-4.15.4

• Add WWW for main site
• Use dynamic SOVERSION for pkg-plist

Test Plan

For every {amd64, i386} × {14.3, 13.5}:

• Successful poudriere testport
• Successful run-testing

[arrowd]

Why bump consumers? There seems to be no need in that.

[alven]

I just was not sure when it's actually needed. Could you, please, explain it to me?

[arrowd]

The release changed the patch version and according to pkg-plist the shared library version wasn't bumped. This usually means that there is no need to recompile consumers, thus no bumps needed.

[alven]

This may seems so as I used dynamic SOVERSION. If it wasn't the case the diff would be:
-lib/libz3.so.4.15.3.0
+lib/libz3.so.4.15.4.0

May be unlike major-/minor-level changes just patch-level changes are safe without dependencies bump?
I don't like to do more work than actually needed :) Just need to know which changes are/aren't safe...
Whether it's safe for me to use dynamic SOVERSION at all? (as one wouldn't be able to see actual .so version change)

[arrowd]

What does readelf -d /usr/local/lib/libz3.so | grep SONAME say for the updated port?

[alven]

In D53474#1220993, @arrowd wrote:

What does readelf -d /usr/local/lib/libz3.so | grep SONAME say for the updated port?

0x000000000000000e SONAME Library soname: [libz3.so.4.15]

Seems like I've got it: no actual SONAME change, so no need to update the dependencies. OK.

[alven]

No actual SONAME change, so no need to update the dependencies

[arrowd]

In D53474#1221017, @alven wrote:

Seems like I've got it: no actual SONAME change, so no need to update the dependencies.

Exactly.

[alven]

@yuri: Could you, please, review this? I can't commit it without your signature :)

[arrowd]

It'd be great to finally land this.

[alven]

Sure! Just all my mentors are busy now so I'm waiting for their review...