Page MenuHomeFreeBSD

math/z3: Update 4.15.3 => 4.15.4
AcceptedPublic

Authored by alven on Oct 30 2025, 2:24 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Jan 19, 5:10 AM
Unknown Object (File)
Mon, Jan 19, 3:30 AM
Unknown Object (File)
Thu, Jan 15, 2:59 AM
Unknown Object (File)
Dec 9 2025, 12:09 AM
Unknown Object (File)
Nov 24 2025, 10:06 PM
Unknown Object (File)
Nov 23 2025, 9:13 AM
Unknown Object (File)
Nov 21 2025, 8:36 AM
Unknown Object (File)
Nov 20 2025, 5:36 PM
Subscribers
None

Details

Reviewers
arrowd
db
yuri
Summary
Test Plan

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

  • Successful poudriere testport
  • Successful run-testing

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 68291
Build 65174: arc lint + arc unit

Event Timeline

alven requested review of this revision.Oct 30 2025, 2:24 PM
alven created this revision.

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

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

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.

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)

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

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.

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

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

Exactly.

This revision is now accepted and ready to land.Oct 30 2025, 6:38 PM

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

It'd be great to finally land this.

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