Skip to content

Use the full project version as library version#50

Merged
msteinert merged 1 commit into
mainfrom
full-libversion
Sep 9, 2025
Merged

Use the full project version as library version#50
msteinert merged 1 commit into
mainfrom
full-libversion

Conversation

@rdmark

@rdmark rdmark commented Sep 7, 2025

Copy link
Copy Markdown
Collaborator

The library version is used for instance by pkgconf to detect dependency versions, so it makes more sense to use the full project version here rather than a static version string that indicates ABI compatibility

The library version is used for instance by pkgconf to detect dependency versions, so it makes more sense to use the full project version here rather than a static version string that indicates ABI compatibility
@rdmark
rdmark requested a review from msteinert September 7, 2025 12:45
@sonarqubecloud

sonarqubecloud Bot commented Sep 7, 2025

Copy link
Copy Markdown

@rdmark

rdmark commented Sep 7, 2025

Copy link
Copy Markdown
Collaborator Author

The results on f.e. Linux in a dynamic library named libbstring.so.1.0.2 rather than the previous libbstring.so.1.0.0

I noticed this situation while working on Debian deb packaging for bstring. This is how meson by the way of pkgconf detects bstring v1.0.2

Run-time dependency bstring found: YES 1.0.0

@github-actions

github-actions Bot commented Sep 7, 2025

Copy link
Copy Markdown

File Coverage Lines Branches
All files 68% 73% 63%
bstring/bstraux.c 55% 64% 46%
bstring/bstrlib.c 73% 76% 69%

Minimum allowed coverage is 50%

Generated by 🐒 cobertura-action against e9abff6

@msteinert
msteinert merged commit 389837e into main Sep 9, 2025
16 checks passed
@rdmark
rdmark deleted the full-libversion branch September 11, 2025 21:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants