novafunc@discuss.tchncs.de to Linux@lemmy.ml · 21 days agoUbuntu/Snap Permissions Prompting: A Deep Divediscourse.ubuntu.comexternal-linkmessage-square18fedilinkarrow-up148arrow-down13
arrow-up145arrow-down1external-linkUbuntu/Snap Permissions Prompting: A Deep Divediscourse.ubuntu.comnovafunc@discuss.tchncs.de to Linux@lemmy.ml · 21 days agomessage-square18fedilink
minus-squareatzanteol@sh.itjust.workslinkfedilinkEnglisharrow-up3arrow-down6·21 days ago The fact that I can’t “update” my software without closing it first. Why can I do that with all other package formats? I get it won’t be the new version until I reopen the app Asked and answered.
minus-squareWilmo@lemmy.mllinkfedilinkEnglisharrow-up4arrow-down1·19 days agoNot really though? Or rather - then answer the other half. Why are flatpaks, deb, rpm, arch, etc. ALL able to update in place? But with snaps we need that sucker closed? It sucks to use like that.
minus-squareatzanteol@sh.itjust.workslinkfedilinkEnglisharrow-up2arrow-down3·19 days agoBecause the app isn’t updated until it’s restarted. Do you think you applied that Firefox security update because you updated the flatpak? Because you haven’t if you left your browser running.
minus-squareWilmo@lemmy.mllinkfedilinkEnglisharrow-up4·edit-219 days agoDid I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. I don’t care if Firefox isn’t updated until I restart it. I just don’t want that terrible workflow: Click update all. Firefox is open, therefore won’t update until you close it and click update again. Every other package manager: Click update. All apps update. When I am ready to close Firefox it’ll be updated next time I use it.
minus-squareatzanteol@sh.itjust.workslinkfedilinkEnglisharrow-up1arrow-down2·19 days ago Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good. Hence my “asked and answered” response. 🙄
minus-squareitslilith@lemmy.blahaj.zonelinkfedilinkarrow-up3·17 days agothe question asked was “why can’t snap do this thing, that every other package manager can” stop being obtuse on purpose.
minus-squarebrax@sh.itjust.workslinkfedilinkarrow-up3arrow-down1·19 days agoThe problem is that you have to break your workflow to update shit, or you have to do updates multiple times to work around the things you’re doing.
Asked and answered.
Not really though? Or rather - then answer the other half. Why are flatpaks, deb, rpm, arch, etc. ALL able to update in place? But with snaps we need that sucker closed? It sucks to use like that.
Because the app isn’t updated until it’s restarted.
Do you think you applied that Firefox security update because you updated the flatpak? Because you haven’t if you left your browser running.
Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good.
I don’t care if Firefox isn’t updated until I restart it. I just don’t want that terrible workflow:
Click update all. Firefox is open, therefore won’t update until you close it and click update again.
Every other package manager: Click update. All apps update. When I am ready to close Firefox it’ll be updated next time I use it.
Hence my “asked and answered” response. 🙄
the question asked was “why can’t snap do this thing, that every other package manager can”
stop being obtuse on purpose.
The problem is that you have to break your workflow to update shit, or you have to do updates multiple times to work around the things you’re doing.