Its even worse when you force Firefox to use wayland its icon doesn’t even show.

Edit: Oh since everyone now is confused; I only have the flatpak version of Firefox installed yet it doesn’t use the pinned icon and doesn’t even use the firefox icon under wayland at all.

  • @BeigeAgenda@lemmy.ca
    link
    fedilink
    21 year ago

    Aside from the kernel you still need most libs, including glibc so it’s a OS without the kernel.

    Next evolution will then be to use flatpak from within flatpak or what?

    • igorlogius
      link
      fedilink
      English
      41 year ago

      OS without the kernel

      just thought you wanted to use the term OS in a way that people will understand you. Saying OS without the kernel … sounds to me like i want a sandwich without filling .... .

      Next evolution will then be to use flatpak from within flatpak or what?

      Is this a joke about para-virtualization? - anyway, i think flatpaks abstraction and isolations make sense. Not to much and not to little. Just enought to keep an application isolated from the basesystem while using portals to interact with necessary apis.

      • @BeigeAgenda@lemmy.ca
        link
        fedilink
        11 year ago

        Using the word OS puts across my point, because when you start packaging your toolchain with glibc and whatever libs you need for your application, you end up with a good part of the Linux file system. Yes there’s missing services and so on but they could run if needed.

        It’s not a virtualization joke, it’s more of a “we put flatpak in your flatpak so you can flatpak while you flatpak” recursion joke.

        • qaz
          link
          fedilink
          21 year ago

          Most system libraries are included in runtimes that are shared among applications.

          • @BeigeAgenda@lemmy.ca
            link
            fedilink
            11 year ago

            Sounds more and more like flatpak is a distribution atop of a distribution.

            Good you can share libs, although I can’t see sense in sharing more than the absolute basic libs, and even then some applications will need different versions of the basic libs.

              • @BeigeAgenda@lemmy.ca
                link
                fedilink
                11 year ago

                From what I gather nix is more of a next generation package manager than a application container/sandbox which means potential security problems with old libs could be less, or rather they are probably at the same level as rpm/deb.

                I don’t see any problems with rpm/deb/etc. ending up getting the boot by nix or another package manager just because they are better, that’s just evolution.

                As someone said about flatpak/snap that their ‘hidden’ strength is distribution of proprietary software, that’s fine by me if that’s the main usage of them.

                The sandbox feature can be solved by SELinux/docker/and several other ways depending on usecase.

                • qaz
                  link
                  fedilink
                  11 year ago

                  Sandboxing is not the main feature of Flatpak/Snap, being able to ship an app for various distributions without having to configure them separately is. Docker/Podman can do that, but then you would actually be shipping an entire distro.

                  • @BeigeAgenda@lemmy.ca
                    link
                    fedilink
                    11 year ago

                    Regarding docker/podman that’s why I wrote depending on usecase, for servers it makes sense to distribute because of scalability, on a single user OS it does not.

                    From what you write I guess that nix does the distribution part of flatpak, so that seems fine, there’s probably a catch/limitation somewhere, there usually is, but it could be an acceptable one.