@ilpianista I was just searching for a client that could publish to both Twitter and Mastodon and Choqok looks the most likely. However, I do not run KDE and generally try to avoid installing any of the QT dependencies. That said, recently I've taken to digiKam via Flatpak. Is packing Choqok like this on the horizon? Thanks!
@ntnsndr @ilpianista Linguistic preference mostly, Flatpak commands fit my lexicon more closely than Snap. Generally not a fan of the AppImage approach, it removes the gains that package managers provide. Nix/Guix would be my personal ideal, but they are a bit out of reach for end-users right now. Aside from all of that, the goals that I have in mind before packaging someone else's project mostly target ease-of-use and portability with minimum additional overhead.
@salt @ntnsndr Great work! You should file a PR in the #KDE applications repo: https://invent.kde.org/packaging/flatpak-kde-applications/
@salt i don't see how installing KDE dependencies 2 times in separate flatpaks is better than installing them once with the systems package manager
@davidak realistically, I'm trying to keep all non-system components outside of the package manager. I think this will lead me to NixOS before too long...
@salt non-system components like end-user software? you don't want to install them with your systems package manager? what is wrong with that? you will end up with the same dependencies multiple times in slightly different versions, but many outdated with security issues..... that will require more resources for no good reason
#NixOS is nice for having a reliable base system using the stable channel and still selectively install the latest versions from unstable
@rothair i haven't tried flakes yet. since it might replace channels at some point, it is probably possible
@davidak yes, like end-user software. The problem as I see it is that you need to have up-to-date components for up-to-date end-user applications. However, those components may not have the same level of stability and security auditing as their predecessors. Thus, the solution seems to be to add an abstraction layer, while still utilizing a package manager framework to handle particular package dependencies.
A Fediverse instance for people interested in cooperative and collective projects.