741
submitted 4 months ago by renzev@lemmy.world to c/linuxmemes@lemmy.world
you are viewing a single comment's thread
view the rest of the comments
[-] RmDebArc_5@sh.itjust.works 10 points 4 months ago

Valid solution, but I miss unified updates with appimages and such

[-] Ephera@lemmy.ml 4 points 4 months ago

Yeah, that's the fun part. Hooking into some auto-update mechanism would be useful to me.

But my stuff is mostly in the scratching-my-own-itch stage, so setting up a FlatHub account, Flatpak metadata, sandbox rules, probably an icon and screenshots and whatnot, and automating the build+releases, just to get auto-updates, yeah... no.

I could code a whole nother project in the time that would take.

[-] ace@lemmy.ananace.dev 3 points 4 months ago

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

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.

this post was submitted on 05 Jul 2024
741 points (93.7% liked)

linuxmemes

21281 readers
710 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!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS