this post was submitted on 05 Jul 2024
789 points (100.0% liked)

linuxmemes

26067 readers
992 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 users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
  • 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, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    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 remove France.

    founded 2 years ago
    MODERATORS
     
    (page 2) 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 9 points 1 year ago (3 children)

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

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

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

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

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

    [–] [email protected] 7 points 1 year 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 1 year 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 1 year 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] 8 points 1 year ago
    [–] [email protected] 6 points 1 year 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)
    [–] [email protected] 5 points 1 year ago (1 children)

    I don't wanna be that guy, but someone has to say it: Nix Flakes

    load more comments (1 replies)
    [–] [email protected] 5 points 1 year ago (3 children)

    People always forget about appimages.

    [–] [email protected] 7 points 1 year ago

    Your security people have not forgotten about appimages. It fills their nightmares.

    [–] [email protected] 5 points 1 year ago (1 children)

    Same app in native format: 2MB. As a flatpak: 15MB. As an appimage: 350MB.

    Appimages are awesome, rock solid, and I have a few on my system, but flatpak never gave me any problem and integrates better with my KDE, and is smaller. Both have their advantages tho. I'm fine with using both. If you are a developer, make a flatpak or an appimage i dont really care just make your software available for linux. Both are fine, choose the one that fits your specific app the most.

    But I also think appimages deserve the same attention and great integration with the OS as flatpaks. Stuff like that AppImageLauncher functionalities should just be integrated inside the DE itself.

    But we need an universal package format for linux asap. Flatpak is on the front in this race, and I'm fine with it. Appimages second, for sure.

    load more comments (1 replies)
    load more comments (1 replies)
    load more comments
    view more: β€Ή prev next β€Ί