A patch for optimizing GIMP 3.0+ for Adobe Photoshop users, including features like:

  • Tool organization to mimic the position of Adobe Photoshop;
  • New Splash Screen;
  • New default settings to maximize space on the canvas;
  • Shortcuts similar to the ones in Photoshop for Windows, following Adobe’s Documentation;
  • New icon and Name from custom .desktop file.

https://github.com/Diolinux/PhotoGIMP/blob/master/screenshots/photogimp_3_-_diolinux.png

Flatpak (Linux)

In order to install the newest version of PhotoGIMP on your Linux operating system using Flatpak, just follow this simple steps:

  • Make sure you already have GIMP installed from Flathub; (for Ubuntu/Mint user just select Flatpak below the install button in the manager)

  • Start and quit GIMP after you installed before you continue!

  • Download the files from this repository or just click here - > https://github.com/Diolinux/PhotoGIMP/releases/download/3.0/PhotoGIMP-linux.zip

  • Extract the content of the zip file on your home folder (.config and .local - they are the important ones) and overwrite the files if needed; (if you can’t see the file click Ctrl+H to see hidden files)

-You’re done, enjoy it! 😄

  • moonpiedumplings@programming.devEnglish
    1·
    1 day ago

    From flahubs docs: https://docs.flathub.org/blog/app-safety-layered-approach-source-to-user#reproducibility--auditability

    The build itself is signed by Flathub’s key, and Flatpak/OSTree verify these signatures when installing and updating apps.

    This does not seem to be optional or up to the control of each developer or publisher who is using the flathub repos.

    Of course, unless you mean packages via flatpak in general?

    Hmmm, this is where my research leads me.

    https://docs.flatpak.org/en/latest/flatpak-builder.html#signing

    Though it generally isn’t recommended, it is possible not to use GPG verification. In this case, the --no-gpg-verify option should be used when adding the repository. Note that it is necessary to become root in order to update a repository that does not have GPG verification enabled.

    Going further, I found a relevant github issue where a user is encountering an issue where flatpak is refusing to install a package that is not signed, and the user is asking for a cli flag to bypass this block.

    I don’t really see how this is any different from apt refusing to install unsigned packages by default but allowing a command line flag (--allow-unauthenticated) as an escape hatch.

    To be really pedantic, apt key signing is also optional, it’s just that apt is configured to refuse to install unsigned packages by default. So therefor all major repos sign their packages with GPG keys. Flatpak appears to follow this exact same model.

    • quick_snail@feddit.nl
      1·
      5 hours ago

      I still fail to see anything that clearly States that all packages in the repo are signed, and that the client is configured to refuse to install any packages that aren’t signed, by default

      • moonpiedumplings@programming.dev
        1·
        4 hours ago

        Idk what to tell you. I linked to sources showing that flathub signs everything, and that flatpak refuses to install unsigned packages by default.

        If you have anything contrary feel free to link it.

        Also you multi replied to this comment. Sometimes I had this issue with eternity.

    • quick_snail@feddit.nl
      1·
      5 hours ago

      I still fail to see anything that clearly States that all packages in the repo are signed, and that the client is configured to refuse to install any packages that aren’t signed, by default

    • quick_snail@feddit.nl
      1·
      5 hours ago

      I still fail to see anything that clearly States that all packages in the repo are signed, and that the client is configured to refuse to install any packages that aren’t signed, by default