#pkgconf 2.9.92 (3.0 release candidate 3) has been released.

tarballs and windows MSI packages are available on distfiles.ariadne.space

#pkgconf 2.9.90 has been released, mostly to test the release machinery since I've moved to a new colo box.

assuming there are no regressions, pkgconf 3.0 will be released in a few days. please test.

tarball (gz): https://distfiles.ariadne.space/pkgconf/pkgconf-2.9.90.tar.gz
tarball (xz): https://distfiles.ariadne.space/pkgconf/pkgconf-2.9.90.tar.xz

the new release includes windows binaries that are compatible with windows 7 or later (windows 8.1 on ARM).

windows x86: https://distfiles.ariadne.space/pkgconf/pkgconf-x86-2.9.90.msi
windows x64: https://distfiles.ariadne.space/pkgconf/pkgconf-x64-2.9.90.msi
windows arm64: https://distfiles.ariadne.space/pkgconf/pkgconf-arm64-2.9.90.msi

latest #pkgconf 3.0 enhancement: the link.abi tag

different libraries are built with different programming languages, for example, one library might be C, while another might be C++ and another might be fortran. these languages have different ABIs and linking requirements.

how do we know how to link the final program in these cases?

in the past, you had to figure it out by hand and hardcode it in your build system.

now... you can do pkgconf --link-abi <modules> and get an output like:

$ ./pkgconf --link-abi --with-path=tests/lib1 foo link-abi-multi
c c++ fortran

this tells the build system what ABIs it is dealing with, although how it should deal with them remains up to the build system.

please add link.abi tags to your C++ and fortran modules, it is backwards compatible :)

working through the rest of the claude mythos #pkgconf 'findings'

some of these are pretty meh πŸ™ƒ

#pkgconf 3 will ship with a fairly exhaustive libpkgconf testsuite written by @Elizafox, this is on top of our declarative tests which were ported from kyua.

thanks to quansight labs for giving us a grant to work on this and SBOM support in pkgconf :)

@danirabbit I am using it to administer a grant to #pkgconf relating to SBOM work. The person doing the work covered by the grant invoices the collective and then I approve it once we come to an agreement for the invoice amount based on the scope of work for each phase.

πŸŽ™οΈ Whoever placed a bunch of big tables and benches at the ULB parkinglot rocks, having those allowed us to record a podcast featuring fifteen (!) people sharing their experiences on FOSDEM Sunday. Lots of folks from postmarketOS and special guests:

* @ariadne from Alpine Linux
* @flypig from Sailfish OS
* @1peter10 from LINMOB.net

Huge thanks to @williamtries and @tgm for editing this episode!

https://cast.postmarketos.org/episode/47-FOSDEM-2026-special/

#fosdem #postmarketos #linuxmobile #newpipe #pine64 #sailfishos #pkgconf

#47 FOSDEM 2026 Special

Aiming for a 10 year life-cycle for smartphones

postmarketOS Podcast

i have added a #muon build to #pkgconf CI. the goal of this is to allow us to begin thinking about deprecating the autotools-based build system.

this won't happen until next year, most likely, but muon is sufficiently complete at this point that i think it solves the bootstrapping problem enough that we can start thinking about getting rid of the autotools stuff, probably in pkgconf 3.1 or so.

anyway #pkgconf users can use X-ESRB-Rating or whatever, I guess. πŸ™ƒ

would an annual (or perhaps semi-annual) #pkgconf distributions meeting be useful?

(and if you have thoughts, reply here?)

yes
54.5%
no
45.5%
Poll ended at .