Thank you Andreas,
Yes, I generally understand semantic versioning, and major-version updates coming with API breaks. What made it the challenge was the SNAFU with the additional vendor/vendor directory going unnoticed for a time and wondering why the update of both the driver and library hadn’t played nicely together.
It’s the proverbial 3-legged stool, with the database, the driver and the PHP library all being separate legs of the stool. In this case the PHP library is packaged by Archlinux rather than being a manual pecl install. The driver being composer, and eventually pie as you indicate.
The primary concern with the 3rd web-installers isn’t difficulty with ensuring the proper version, but concern over supply-chain compromise. Between the recent and repeated PyPi and npm compromises, you add github to the list and “confidence” in secure delivery for a server interface is a big concern. That could be alleviated by simply providing a direct download of the driver package in archive format. At least in my case the driver file size is trivial, less than 2M total installed.
Thank you for your detailed and thorough explanation!
