this post was submitted on 05 Jul 2024
742 points (93.9% liked)

linuxmemes

21263 readers
2021 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    742
    Flatpak haters seem to believe that if an app isn't on their distro's repos, it's the developers' fault. (lemmy.world)
    submitted 4 months ago by renzev@lemmy.world to c/linuxmemes@lemmy.world
    200 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] ace@lemmy.ananace.dev 3 points 4 months ago (1 children)

    Well, if you have any form of build script, makefile, or CI, then you can easily shove that into a flatpak-builder manifest and push the build repo anywhere you want. The default OSTree repository format can be served from any old webserver or S3 bucket after all.

    I've done this for personal projects many times, since it's a ridiculously easy way to get scalable distribution and automatic updates in place.

    [โ€“] Ephera@lemmy.ml 1 points 4 months ago (1 children)

    Hmm, okay, that doesn't sound too bad.
    Does the sandboxing get into the way much? Can a user tell it to poke a hole into the sandbox, to use some specific folder, for example?

    I think, my real problem is that I don't actually use Flatpak for any software I have installed. ๐Ÿ˜…
    I'm not opposed to using Flatpak, but I disabled Flathub pretty quickly on my distro's software store thingamabob, when I accidentally installed some proprietary software from it. Fuck that shit, no matter how much sandboxing I get.

    [โ€“] ace@lemmy.ananace.dev 3 points 4 months ago

    In regards to sandboxing, it only gets as far in the way as you ask it to. For applications that you're not planning on putting on FlatHub anyway you can be just as open as you want to be, i.e. just adding / - or host as it's called - as read-write to the app. (OpenMW still does that as we had some issues with the data extraction for original Morrowind install media)

    If you do want to sandbox though, users are able to poke just as many holes as they want - or add their own restrictions atop whatever sandboxing you set up for the application. Flatpak itself has the flatpak override tool for this, or there's graphical UIs like flatseal and the KDE control center module..