I don't think I ever used the cli tool I usually use the flapak gui tool but this seems pretty nice
I don't think I ever used the cli tool I usually use the flapak gui tool but this seems pretty nice
Ri think it's a good idea
Respecially for a security feature
Mesp for being a small package
Rusing an unverified flatpak or an appimage is 
Moof did not know it was unverified
Ryup
RRyou can scope flathub down to the verified subset btw
Rif you want to avoid ever installing unverified
Mthats neat that they provide that
RRIs @bsherman around? looking for a yes or no on a PR
Rdon't even need a review
Rjust buy-in on the idea, or a "no"
Rkind of in limbo otherwise
Jbsherman's been on holiday the past few weeks
Rah that explains it, I'll wait a bit
Rthanks for letting me know
EYeah I saw afterwards, I installed Yubikey Auth from Flatpak and I like it
IYes, I meant that brew only packages Zed for MacOS
RThose are casks
RThey're not actually on brew
RJust a wrapper to install it from app store usually
RIt's like winget on windows
RIt wouldn't really work on Linux unless you integrated it with appimage or flatpak
JI'd love for someone to make a brew plugin that just replaced casks with flatpaks when on linux
RThere's probably a way to do it with a fish function
Ralias brew-install-cask='flatpak install'Kinda cursed tho
Jnah we'd need a proper plugin
RUblue revolves around Flatpaks, and most CLI applications aren't available as a Flatpak. Homebrew contains thousands of CLI packages and libraries, and it works effectively in userspace on atomic/immutable systems, making it the perfect pair
RTogether, Flakpak covers GUI and Homebrew covers CLI. Other solutions like distroboxes and layering just fill in the gaps
Ahttps://discord.com/channels/1072614816579063828/1074422586894712912/1276562855604391997
what do you think about this
what do you think about this
ROof, this is something the entire ublue team needs to look at
RSomeone should go in there and inform them of our use case
RIt would be unfortunate if Homebrew declares us as unsupported
HMy 2 cents is it would fall on fedora and brew to sort it out.
We don't do anything special.
But I think it is more on brew to fix. If home is a symlink then follow the link to the absolute path (or just assume atomic and look in /var/home)
Not rocket science
We don't do anything special.
But I think it is more on brew to fix. If home is a symlink then follow the link to the absolute path (or just assume atomic and look in /var/home)
Not rocket science
Ayeah, i would love to PR but i dont understand ruby lol
Aalso the problem doesnt sound that complicated
HSame
Lsame
La workaround that might work is to use a bind-mount instead of symlink
Awell my problem has workaround but i fear for future problem
LI don't know ennough, yet, tho, about how silverblue is set up
HThen the ball is in fedoras court since the installer does a symlink.
Also bind mounts don't work for composefs so doubt it will happen
Also bind mounts don't work for composefs so doubt it will happen
Laha. gotcha. it's a symlink to allow overlaying?
ZSometimes, containers have limitations when it comes to accessing hardware
ZSo my guess is it acts as a fallback on those cases
ZPlus, though personal opinion, not everyone can bother to open a container just to install a simple CLI program
AIt's because bluefin is targeted also at Mac users and they use brew
