this post was submitted on 05 Jul 2024
739 points (93.8% liked)

linuxmemes

21197 readers
94 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
     
    (page 2) 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 8 points 4 months ago
    [–] [email protected] 8 points 4 months ago (3 children)

    I just distribute it as a self-contained executable/archive. ¯\_(ツ)_/¯

    [–] [email protected] 10 points 4 months ago (1 children)

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

    [–] [email protected] 4 points 4 months ago (3 children)

    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.

    load more comments (3 replies)
    [–] [email protected] 7 points 4 months ago (1 children)

    As long as your application is statically linked, I don't see any issue with that.

    [–] [email protected] 8 points 4 months ago (3 children)

    So, like, dumb question. People here assumed that I mean AppImages, whereas I actually meant just a statically linked binary. Is that really the only reason why AppImage exists? So, that dynamically linked applications can be distributed like statically linked ones?

    [–] [email protected] 9 points 4 months ago (5 children)

    You cannot statically link everything. Take graphics libraries and APIs for example, do you statically link against nvidia's or mesa's opengl?

    load more comments (5 replies)
    [–] [email protected] 6 points 4 months ago (1 children)

    The majority of AppImages I've seen have been dynamically linked, yes. But it's also used for packaging assets.

    load more comments (1 replies)
    load more comments (1 replies)
    load more comments (1 replies)
    [–] [email protected] 6 points 4 months ago (1 children)

    Nix: you package it yourself and do a pull request

    Sadly, many flatpaks don't even work on NixOS properly because of assumptions about the file structure or similar

    load more comments (1 replies)
    load more comments
    view more: ‹ prev next ›