no worries! it can be a bit goofy to get used to an OStree system when you are used to doing things
no worries! it can be a bit goofy to get used to an OStree system when you are used to doing things a certain way.
NThis is always a great option as well!
Myep, I'm used to the usual package managers like yum/apt/packman/homebrew
NHomebrew should be available on Bazzite by default as well, I can't remember if VSCode is in Homebrew or not though.
NI layer the RPM in my custom image. Typically you only want to layer packages if you can't solve it by installing either the flatpak, distrobox, or brew.
NSaw this in Matrix. How many of us use App images? I do for some things, but not many. https://github.com/fedora-silverblue/issue-tracker/issues/589
GitHub
Describe the bug rpm-ostree 2024.7-1.fc40 drops the fuse dependency leading to a removal of fuse in Silverblue 40. Changelog: - Require fuse3 as ostree now uses it Removed: fuse-2.9.9-21.fc40.x86_6...
KWell that's an easy fix on our end
KOne PR to Main to make sure that package is included
Bhonestly to me this is a nonissue, more dstros should jsut stop shiping that fuse 2.9.9 as it is depricated and its only appimage creator who doesnt want to move and insists that everyone should conform to him
Tbazzite users use appimages
Tbut otherwise i agree
Tflatpak is the only universal linux graphical package option i care about
KGitHub
fedora-silverblue/issue-tracker#589
Nto be clear, Fedora Upstream is thinking about potentially still keeping it.
Nthey are just having the discussion.
Kthat one line just ensures we always have it
Kso no big deal
Rwho are the current maintainers for ublue-os/config and ublue-os/ucore?
https://github.com/ublue-os/config/pull/297
https://github.com/ublue-os/config/pull/313
https://github.com/ublue-os/ucore/pull/187
Please review or decline
The first one has been waiting for some time
https://github.com/ublue-os/config/pull/297
https://github.com/ublue-os/config/pull/313
https://github.com/ublue-os/ucore/pull/187
Please review or decline
The first one has been waiting for some time
Rthanks @Kyle Gospo 
Rjust need another (for config)
Rngl appimage support should be dropped eventually
Rfuse2 is unmaintained and is yet another suid binary
Ti don't think this will happen in the near future
Rsadly
Tbazzite tries to reach parity with steamos and tons of applications are appimage only
Thhd-ui is also an appimage and we rely on that
Rbut still it would behoove bazzite to start pushing the apps that are appimage-only to package in another format
Reven if appimage deprecation is a year+ away
KWe support appimages because it's common on SteamOS
Kwe do not have the weight to fix that
RI see
Reven still, it would be nice to eventually remove fuse from main
KAlso, we have an added issue that the OpenRGB flatpak is unoffiical
Tthe amount of people who use emudeck alone would be very upset
Rand keep it in bazzite only
Kand it displays a warning about missing udev rules every time it's launched
Kwhen pressed, OpenRGB's devs told us it's not supported and to use the appimage
Kso, that's gonna fuck over a lot of people too
Kthen you have companies like Wooting that only release their software as AppImage on linux
Ryeah fair
Kand you're stuck -- have to support it
Rfor bazzite it makes sense
Tso many modding tools too
Twe'll never escape it lmao
Rbut for main if Fedora drops appimage support i think ublue should as well (aside from bazzite)
Rotherwise ublue would be encouraging the perpetuation of fuse2
Rplus, users can always layer fuse2 back
Klooks like the appimage dev's solution is to statically compile fuse2
Rthat's not really a solution lol
FAppImage is easier to make than flatpak, so I understand why some devs prefer it
Rappimage would be okay if they just migrated to fuse3
