• Mane25@feddit.uk
    2·
    1 year ago

    Finally! I have a lot of good will towards this project and understand there can be setbacks, but having been lead to believe that the Flathub version would be the flagship release channel, and then waiting for almost a month for the big new release without explanation of the delay it’s not been a great look to be honest… hopefully they can seriously sort this out in future.

      • dino@discuss.tchncs.de
        1·
        1 year ago

        I totally agree being a contrarian outcast, but not because of what I commented earlier. Why would I use flatpak thunderbird when there is version in my repos which just needs to be updated?

  • zacher_glachl@lemmy.world
    11·
    1 year ago

    flatpak mask org.mozilla.Thunderbird until the “hide title bar” flag works again. I’m not losing two lines of display space to eye candy.

  • darcmage@lemm.eeEnglish
    0·
    1 year ago

    Flathub still shows the old version and the github page has been archived. The main site doesn’t even have an option to choose your download package.

    I’ve already installed 115 but this doesn’t seem new user friendly.

      • SafetyGoggles@feddit.de
        1·
        1 year ago

        I believe it’s mentioned in an issue in the official Thunderbird repo that from now on the Flatpak is maintained by the main Thunderbird dev team, so the Flatpak repo is archived and all Flatpak packages from now on will be uploaded directly by the devs.

        • ebits21@lemmy.ca
          1·
          1 year ago

          Yeah this. The official devs took over. Why the delay happened in the first place.

    • ax1900kr@lemmy.worldOPEnglish
      2·
      1 year ago

      Generally speaking, the advantages of Flatpaks are:

      -The developers only need to maintain and release one version

      -It’s sandboxed, for each app you can decide which parts of your filesystem are exposed, which env variables, which types of inter-process communications, etc

      -You kinda avoid dependency hell. You can use old unmaintained packages because Flatpak will provide old versions of their dependency if they’re needed, while at the same time avoiding unnecessarily duplicated packages

      -All installed apps are in your .var folder instead of being system-wide. Every app has its own folder with its own .config and .local/share inside, with their respective config files and data

      -It supports partial updates

      -It doesn’t require root permissions to use

      -It lets you use the most recent software even in really old LTS systems like Debian, and the Flatpaks updates are usually as quick as rolling release distros

      -You don’t need to abuse PPAs or the AUR

      -It makes your system updates actually faster since you’ll have less system packages, and you’ll be able to update your big apps separately

      I may be missing some, but those are the most important to me

      • maess@feddit.deEnglish
        01·
        1 year ago

        But they don’t adhere to the system theme at all so every time I launch a flatpak it is white if it uses GTK; and they are annoying to launch via command line.

        • Yote.zip@pawb.socialEnglish
          1·
          1 year ago

          You can theme them with some overrides: https://itsfoss.com/flatpak-app-apply-theme/

          I throw this in my .local/share/flatpak/overrides/global file in order to enable theming (the override directory may require flatseal? I forget):

          [Context]
filesystems=~/.icons:ro;~/.themes:ro;xdg-config/Kvantum:ro;~/.config/gtk-3.0:ro

[Environment]
QT_STYLE_OVERRIDE=kvantum
GTK_THEME=

          Then you can put your stuff in your personal ~/.themes and ~/.icons directories

          As for calling via command line, you can use something like this or just manually make aliases.