Skip to content

Release Linux builds through common app stores via Flatpak/AppImage/Snap/Nix packages #584

Open

Description

@13hannes11

It would be great to have an installable editor, for example as Flatpak or AppImage.

Activity

  1. Keavon commented on Apr 17, 2022

    @Keavon
  2. 13hannes11 commented on Apr 17, 2022

    @13hannes11
    Author
  3. Keavon commented on Apr 18, 2022

    @Keavon
  4. moved this from Short-Term to Longer-Term in Task Boardon Jan 4, 2024
  5. alerque commented on Mar 29, 2024

    @alerque
  6. Keavon commented on Mar 29, 2024

    @Keavon
  7. joewood9364 commented on May 12, 2024

    @joewood9364

    Please focus on Flatpak as this will make it compatible with atomic desktop like Silverblue, Aeon etc. and Flathub is great for discoverability.

  8. 18 remaining items

  9. added
    DesktopNative desktop API work with Windows/Mac/Linux and CEF
    on Aug 4, 2025
  10. moved this from Backlog to Distribution in Desktop Applicationon Aug 4, 2025
  11. moved this from Blocked to Short-Term in Task Boardon Sep 2, 2025
  12. changed the title [-]Release Linux builds through common app stores via Flatpak/AppImage/Snap packages[/-] [+]Release Linux builds through common app stores via Flatpak/AppImage/Snap/Nix packages[/+] on Dec 16, 2025
  13. Keavon commented on Dec 22, 2025

    @Keavon
    Member
  14. alerque commented on Dec 22, 2025

    @alerque

    Not all of those are "app stores" per se.

    Flathub, Snapcraft, and Steam are of course app stores and as an app developer you can target builds for those platforms.

    Arch Linux and Nix are not for various reasons.

    • The official Arch Linux package repository is managed by Arch package maintainers and requires the distro to target you, not the other way around. This is true of most Linux distros — you'll need people on the inside loop of the packaging system to get packages into most systems.

      That being said I am personally an Arch Linux package maintainer, already have graphite-editor-git in the AUR, and will be more than willing to adopt Graphite as an official package as soon as it has a tagged release (probably even if that is an early 0.0.1 or other early cycle release not considered production ready as long as the release process itself looks semi stable.

    • Nix is similar in that it is a distro, but they do accept outside contributions to packages without any particular bars you'll have to cross about notoriety as long as someone from the community sounds like they will be pitching in for updates.

      However you do not have to and should not wait for an official Nix package in the nix-pkgs repository. You should have a Flake in this repository no that anybody with either Nix OS or any distro with a nix package can directly run your app. This can be done any time and doesn't need a tagged release to get started with, and working out the details of the build in the flake will be hugely beneficial to other potential distro packagers, eventually nixpkgs, your own development team to confirm dependencies in a hermetically sound way, and of course to users to be run in a predictable way as nix run github:GraphiteEditor/Graphite.

  15. timon-schelling commented on Dec 22, 2025

    @timon-schelling
    Member

    @alerque Hey, Help with the aur package would be greatly appreciated. You could get started with that anytime you want. Graphite desktop Linux is in a good state. We already have a open nixpkgs PR that might be helpful to get started and identify dependencies.

    Graphite repo has a flake (with desktop app packaged) under .nix. nix run github: GraphiteEditor/Graphite?dir=.nix

    Regarding wording, although AppStores is not technically correct, I'm fine with using that terminology as it might be more meaningful for non-linux people.

  16. alerque commented on Dec 22, 2025

    @alerque

    Hey, Help with the aur package would be greatly appreciated. You could get started with that anytime you want.

    Read my message again. It's already done. It already works. It's currently only a VCS package that builds from Git HEAD at the time people install it because there are no release tags in the repository. As soon as there are I'll be making an official package, so there is no need for a 'stable' edition of the AUR packaging.

  17. timon-schelling commented on Dec 22, 2025

    @timon-schelling
    Member

    Hey, Help with the aur package would be greatly appreciated. You could get started with that anytime you want.

    Read my message again. It's already done. It already works.

    Sorry, I confused your aur package with a outdated one that I saw a couple weeks ago that was building the old tauri based app (very outdated).

    Took a quick look at the PKGBUILD.
    Looks good in general. Two comments:

    1. We don't "mix and match" toolchains. The loocked nightly rust toolchain should only be used for building wgsl shaders (rustgpu requirement, just text files that get included as a string). All other components should be built with stable rust toolchain. If not having two rust toolchains is a hard requirement you could instead use the prebuilt shaders we provide (see nixpkgs PR).
    2. I'm not sure that including graphene-cli in the same package is a good idea.

    The first versioned release is planned for January.

  18. tbaumann commented on Feb 18, 2026

    @tbaumann

    Graphite repo has a flake (with desktop app packaged) under .nix. nix run github: GraphiteEditor/Graphite?dir=.nix

    I'm glad for the nix support. But the subdir syntax ist quite cumbersome. It took me a while to research that actually.
    It would be fantastic if the flake.nix file was moved to the repository root.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

DesktopNative desktop API work with Windows/Mac/Linux and CEFInfrastructureBuild systems and CI

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions