Why not build it from source?

Hi, and thanks for reviewing! I didn't build from source because I don't need it, it's more work, and I don't even have any other platforms to test things.

For nixpkgs generally build from source, since it is then linked correctly (avoids the LD_LIBRARY_PATH environment variable) and we can support platforms as they are added to NixOS. Additionally we can catch more NixOS-related issues of the package while building which often only show themselves when running in the case of prebuilt packages.

Overall the resulting packages are also cleaner and more transparent as to what is going on.

I understand it is more work and it often can be kind of tricky to get more obscure build systems to work with nix. If you don't want to rework it for NixOS, you can still use callPackage from your configuration.nix to use it on your system or override your nixpkgs.

Unfortunately I don't think I'll spend any more time on this any time soon. It does work so I think it should be merged (i.e. I think it's better than not even having a package for this), but if it might cause trouble for maintainers I understand why maintainers wouldn't want to merge it.

Fair enough, as said you can always use overriding to add local packages to nixpkgs for your system.

Probably worth it to also install a matching .desktop file and install it to better integrate it with desktop environments.

Added one in e85a1c1 but tbh I have no idea what I'm doing here... I use i3 so it's been many years since I even consumed these things I think.

Are there so many executables? Maybe also use install to remove the chmod.

As with most .NET apps there's one entrypoint executable plus lots of dll files and other auxiliary files that need to be in the same directory.

Wouldn't it be a good idea to move them into some lib/libexec etc directory and build a wrapper around the main executable? Polluting $PATH with many files even if not executable is not that great.