I love .appimages they work on all distros, easy to install, works from any directory, works without installing

If I can achive this setup it will make switching my work from machine to machine easy-fast, resilient, and distro hopping wouldn’t be a issue.

  • HubertManne@piefed.social
    cake
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 hours ago

    basically the directories just need to be created. right now im using appman to update and to automatically created directories wit -H and -C. Im hoping for the holy grail which is an appman gui program that would do this. There is kinda one but its repo thing is not done as well as with appman. Given how good appman is it makes the most sense if someone does a gui is to just kinda make a gui wrapper for it.

      • wildbus8979@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        7 hours ago

        It’s weird they don’t really really talk about it in the documentation, but yes it sleeps you to change the data path of AppImages

        • Nobody@lemmy.world
          link
          fedilink
          arrow-up
          4
          ·
          7 hours ago

          I’m looking through Gear Lever and don’t see anything. I only see the option to change the path where there actual Appimages are stored, not the data created by the appimages.

  • Nobody@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    7 hours ago

    I see two options.

    The simpler of which is to have a wrapper script that says HOME=/custom/path/for/appimage. Apps that correctly follow xdg-specs will then put all their data in that path. But not all apps will. Apps that put stuff in /home/$USER will not use the correct location.

    The more foolproof way would be using something like bubblewrap, which is used by flatpak. With bubblewrap, the sandboxing can make /home/$USER appear as /custom/path/for/appimage. However, this would take more work to setup, since I presume you want the appimages to feel unsandboxed.