Julian Bender
CoMaps - Hike, Bike, DriveIf you're looking for a map & navigation app on your Linux Desktop: You can now also find CoMaps on Flathub! https://flathub.org/apps/app.comaps.comaps
Ærion@CoMaps
Is there a way to install this without using Flatpak? I avoid Flatpak like the plague.
@aerion you could do the build yourself, the instructions for that are here: https://codeberg.org/comaps/comaps/src/branch/main/docs/INSTALL_DESKTOP.md 🙂
Papa Exmatrikulatus 🏴🏳️🌈@aerion
Quick question: Why do you avoid Flatpaks?
Quick question: Why do you avoid Flatpaks?
@Papaexmatrikulatus
This blog post explains my reasons perfectly.
https://machaddr.substack.com/p/snap-or-flatpak-on-linux-why-you
Pretty much the same reasons why I hate Electron apps.
Bastian@Papaexmatrikulatus @aerion I personally avoid flatpaks (snaps not as much) because of limited system access and therefore usability. The two main things I noticed:
- Missing subpixel anti-aliasing led to worse readability of text in e.g. LibreWolf
- Filesystem access: LibreWolf file downloads failed, KiCad could only open the files when directly opened from the file manager, FreeCAD could not save any files at all (fixed in newer versions though)
Can I fix some of those issues with permission management? Maybe, but I tried for a few minutes and then realised one should just install the native version from whatever package manager one uses
- Missing subpixel anti-aliasing led to worse readability of text in e.g. LibreWolf
- Filesystem access: LibreWolf file downloads failed, KiCad could only open the files when directly opened from the file manager, FreeCAD could not save any files at all (fixed in newer versions though)
Can I fix some of those issues with permission management? Maybe, but I tried for a few minutes and then realised one should just install the native version from whatever package manager one uses
@bas_spr
Exactly, more fiddling required to achieve (partial) parity with native versions. It should make things easier, not harder.
Flatpak, Snap, and AppImage (and Electron) primarily benefit developers, while offering little benefit to users.
Furthermore, it scatters packages over multiple installation sources, instead of just one: the native package manager..
And finally, yet again we have multiple, incompatible, approaches trying to solve the same problem. Until there is a single, unified method for package distribution, that addresses all the shortcomings of the current ones, I'm steering clear of all of them.
@bas_spr @aerion
I don't really understand the part of your argument abour a unified approach: The package manager is a unified approach for Distributions, but not for Linux as a whole. So, here you have Flatpak, where you can install the same version of Delta Chat or other apps the same way accross different distribitions.
I don't really understand the part of your argument abour a unified approach: The package manager is a unified approach for Distributions, but not for Linux as a whole. So, here you have Flatpak, where you can install the same version of Delta Chat or other apps the same way accross different distribitions.
@Papaexmatrikulatus
Unified as in: a single, universal method to install packages, as opposed to Flatpak vs Snap vs AppImage, mixed with native packages. They all try to be that, but none of them actually achieves its goal.
Take CoMaps, for example.
Ubuntu users would, I imagine, prefer a Snap package, but since only a Flatpak (*) is offered, they're either left out or forced to install Flatpak, learn how to use it, and now they have three app sources to maintain: .deb (via apt), Snap, and Flatpak. That's not what I'd call unified.
(*) I don't use any of the *buntus, or their derivatives, so I don't know if someone's made a Snap package. It's more to illustrate the problem.
@bas_spr
@bas_spr @aerion
Ok, but the method you are prefering isn't a unified approach either, because it depends on your distro, so...
I mean, the link you posted above criticises the de jure (Snap) and de facto (Flathub) centralization of these packaging systems, which is a valid.
But why then, do you want a unified approach? Honestly i would only use Snaps if i really had to... But Flatpaks are in my mind at least more or less the standard packages for sandboxing on Linux. Who uses Appimages?
Ok, but the method you are prefering isn't a unified approach either, because it depends on your distro, so...
I mean, the link you posted above criticises the de jure (Snap) and de facto (Flathub) centralization of these packaging systems, which is a valid.
But why then, do you want a unified approach? Honestly i would only use Snaps if i really had to... But Flatpaks are in my mind at least more or less the standard packages for sandboxing on Linux. Who uses Appimages?
@Papaexmatrikulatus
But that has been my point all along: I don't *want* Flatpak et al. I prefer staying with native packages.
*If* there is to be a unified approach at all, it has to address the current issues, the biggest one of which is competing systems. Until then, as I originally stated, I am not interested.
They do not solve a problem for me, they *create* problems.
Also, as previously stated, they primarily benefit devs, as they only have to package their apps once. Just like Electron apps primarily benefit devs.
As for who uses AppImage: https://aur.archlinux.org/packages?O=0&K=Appimage
@Papaexmatrikulatus
System integration, or rather the lack thereof, is only one of the issues with Flatpak/Snap. Even if a package doesn't need it, the other issues mentioned in the article I posted, still apply.
@bas_spr
System integration, or rather the lack thereof, is only one of the issues with Flatpak/Snap. Even if a package doesn't need it, the other issues mentioned in the article I posted, still apply.
@bas_spr
@Papaexmatrikulatus
Well, you asked a 'quick' question as to why I avoid Flatpak.
I gave you my reasons, and they still stand.
If Flatpak, or even Snap (known to have been a source of spyware, BTW) works for you, then great! I'm not trying to convince you, or anyone, to not use it.
I don't really care whether it's one or the other that becomes the standard, as long as the current issues are addressed.
Until such time, I'm not interested, and will stick to native packages that don't bloat my system, and can be installed and updated from a single source.
n2o ☮️@n2o @aerion the build instructions are here: https://codeberg.org/comaps/comaps/src/branch/main/docs/INSTALL_DESKTOP.md 🙂
Luci ☯⚛@aerion @CoMaps There's also an AUR package of course but it seems to need an update in order to build and run correctly 😅
@quantumsys
Perfect, as I happen to run Arch!
Lance@quantumsys @aerion @CoMaps
Yeah. I installed it but cannot get the maps to download. It says they're cued for downloading but there's no way to kick that off and Comaps shows zero network activity.
Yeah. I installed it but cannot get the maps to download. It says they're cued for downloading but there's no way to kick that off and Comaps shows zero network activity.
std::living std::fish@CoMaps YOOOOOOOOOO
@CoMaps Why are preferences placed inside the help menu?
@livefish there's already a list of potential improvements here: https://codeberg.org/comaps/comaps/issues/3387
It just needs enough people with time and the skills. 🙂
Simplify Qt app's UI
### What problem would this feature help solve? Currently, the Qt app's UI is quite complex to a user who doesn't know what all of the icons mean, and some of what the icon buttons do is quite complex. Plus we have a menu bar with a single menu item, "Help", with ways to sign into OSM, etc. ###...
Miguel Torrellas
Deni Mintsaev (mintydev)@CoMaps wait, CoMaps had a desktop version? Or is this the first time it's been released?
@mintydev so far we hadn't packed it anywhere, it's only been on flatpak for ~ a week
mahadevank@CoMaps hey guys a .deb for ubuntu/debian would be nice. If I have some time I'll look into creating it
@mahadevank that would be great, the rate limiting step for us is indeed the volunteer time for supporting more options. Feel free to join us on Codeberg or Zulip if you're planning to move ahead with it! 🙏
Fynn@CoMaps Thanks, something I have been looking for + very convenient using flatpak. 👍
φαггoт
Glob
Michel Stuyts 🌍@CoMaps First thing I tried when reading this, was installing it in WSL, and now I have CoMaps running in Windows without a problem.
@michelstuyts that's great!