On 21.02.21 21:08, Dawid Wrobel wrote:
On Sun, Feb 21, 2021 at 2:42 PM Alexander Maret-Huskinson <a...@maret.de> wrote:
Overall vcpkg does not seem to support versioning,
It does, in fact – it is being readied for a release, but already
supported in the main branch:
https://devblogs.microsoft.com/cppblog/take-control-of-your-vcpkg-dependencies-with-versioning-support/
That is good news, I'll give it a try.
With 16.04 Xenial going EOL in 1 month, shouldn't
we assume that whatever glibc, etc. that 18.04 Bionic LTS provides is
the minimum we're willing to support? KMyMoney is s desktop software,
after all, and it is reasonable to assume that the vast majority of
personal desktop installations no longer use releases from around 2016
– be it Ubuntu's or other vendors'. I don't think supporting older
releases is a hill worth dying on.
Well, I see it a bit differently. Creating a backport of KMyMoney 5.1.1
for Ubuntu Focal took me like 2 minutes. Download Debian source package,
update version, recompile - done. So you can usually find or create
backports easily when your distribution is still compatible dependency wise.
The need for AppImages comes in, when you have to replace half of your
distribution to be able to run an application. By using a modern
distribution to build an AppImg your are basically invalidating its main
use case.
But I guess we have to start somewhere and maybe the situation with
vcpkg improves over time when the ports mature a bit more.
While vcpkg is indeed a fairly bleeding edge piece of software, I
believe most of the issues you described can be attributed to an
attempted usage of Xenial, while their CI/CD infra tests the ports
using 18.04
(https://github.com/microsoft/vcpkg/tree/master/scripts/azure-pipelines/linux).
That is true, that's why I switched my Docker image to Ubuntu Focal
temporarily, just to see this thing compile at least once :-D
All the Best
Alex
