Because distros usually ship only one specific version of a library. And different distros ship different versions of libraries. If you develop your software on Arch Linux targeting a specific version of an API of the library you're using, and another developer tries to build the same software on Debian, and another on Fedora, it's basically a gamble if your software is going to build or not. With vcpkg, you can pin libraries to their specific versions, to ensure that your project builds regardless of the environment.

▲

yjftsjthsd-h 3 days ago | parent [-]

Then when distros go to actually package your software for users it'll break. I'm not sure moving the pain downstream is worse, but I'm also not sure it's better.

▲

cromka 3 days ago | parent [-]

KDE releases all their apps on Windows and amcOS. In fact most of their users are in Windows. Krita makes most money off of Windows Store.

This is why nobody can rely on distro managers. Not to mention FlatPaks and so on.

Lastly, KDE maintains their own Qt fork for packaging purposes.

	▲	reactordev 3 days ago \| parent [-]
		That has nothing to do with it. While both relate to KDE, we are talking about two very different things. You are talking about release channels, we are talking about development headers.