Page MenuHomeFreeBSD

math/z3: Update 4.15.3 => 4.15.4
ClosedPublic

Authored by alven on Oct 30 2025, 2:24 PM.
Tags
None
Referenced Files
F159741754: D53474.id172019.diff
Wed, Jun 17, 6:14 PM
F159726626: D53474.id165451.diff
Wed, Jun 17, 1:46 PM
Unknown Object (File)
Tue, Jun 16, 7:38 PM
Unknown Object (File)
Tue, Jun 16, 1:34 PM
Unknown Object (File)
Tue, Jun 16, 10:26 AM
Unknown Object (File)
Fri, Jun 5, 12:48 AM
Unknown Object (File)
Thu, Jun 4, 6:55 PM
Unknown Object (File)
Sat, May 23, 11:59 AM
Subscribers
None

Details

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 68282
Build 65165: 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...

This revision was automatically updated to reflect the committed changes.