flake: add apps entry and fix runtime error

[TornaxO7]

Fixes the core dump when running rio with nix. @RaySlash you can take a look if you want.

[TornaxO7]

Why is the windows build failing???

[RaySlash]

This seems like an old snippet from old config? What was the motivation for this? However, I just tested this change and seems working on this end. Is this change necessary? I believe that we should not be adding additional functions on functions just for the dependencies. We could add these for PerSystem and see if that would work for us. I did this way of passing function carrying evaluations of dependencies to the function defined by rustPlatform as an experiment mostly. I am not certain if this could cause further breakage. Also, if this is for people to use flakes to generate a package for their config should not be really a concern as nixpkgs is being constantly updated by you and other maintainers as I can see now. I believe nix develop and nix build should be our focus. I would like some clarity regarding this.

[RaySlash]

Also, just adding

pkgs.rustPlatform.buildRustPackage {
   inherit (cargoToml.workspace.package) version;
   name = "rio";
   src = ./.;
   cargoLock.lockFile = ./Cargo.lock;
   
   cargoBuildFlags = "-p rioterm";
   
   buildInputs = runtimeDeps ++ buildDeps;
   nativeBuildInputs = buildDeps;
   runtimeDependencies = runtimeDeps;
   
   buildNoDefaultFeatures = true;
   buildFeatures = ["x11" "wayland"];
   
   meta = {
            description = "A hardware-accelerated GPU terminal emulator focusing to run in desktops and browsers";
            homepage = "https://raphamorim.io/rio";
            license = lib.licenses.mit;
            platforms = lib.platforms.unix;
            changelog = "https://github.com/raphamorim/rio/blob/master/CHANGELOG.md";
            mainProgram = "rio";
    };
};

was not enough to get rid of the issue where it core dumps with NoWaylandLib or NoXCBLib.

[TornaxO7]

This seems like an old snippet from old config? What was the motivation for this? (...) Is this change necessary?

I'm not fully understanding this yet as well, but I assume that working with pkgs instead of an isolating function, as with mkRio here, potentially breaks some things, since callPackage does some "black magic" (that's what I got told of from the unofficial nixos-discord server).

However, I asked on the discourse what the preferred way is to declare a package and it seems to be either to move that into an extra file, as suggested in the nix pills (I only have skimmed through it at the time of writing this) or moving this into a variable, as we do here with mkRio.

I believe nix develop and nix build should be our focus.

I agree, but I'd say that nix run is more important than nix build because what's the point of having a succeeding build, if you can't use it? ;)

[RaySlash]

LGTM