Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Who needs vcpkg when you already have a built in package manager?

If it’s not in the distro, it’s not in the tree, then it’s built by another tool like genie or whatever. vcpkg was because windows had no such capability.

It’s decent but it’s not the best.



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.


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.


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.


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.


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.

And have you ever had to work on different version of libraries for development and LTS branches of software? Because it doesn't sound like you had? Lastly, KDE maintains their own Qt fork for packaging purposes.


Everything you just said was irrelevant and followed by a personal attack.

>”Because it doesn’t sound like you had?” was unnecessary and you have no idea who I am.

I was merely stating that most distros have those headers, most distros care about being up to date with stable releases. Yes KDE releases software on Mac and windows, that has nothing to do with vcpkg. If anything, it’s more work.

I’m sick of the “mansplaining” in these comments like I was born yesterday. I wasn’t, and I know how to write C.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: