Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've written and tested a flake.nix for FUTO.MDNS
It appears to build FUTO.MDNS as Grayjay.ClientServer expects, but I can't be sure until I test it on
Grayjay.Desktop/Grayjay.ClientServer/flake.nix
. If someone with more knowledge of dotnet's intricacies (and.csproj
files in partilcular, namely Grayjay.ClientServer.csproj) could verify this, I would appreciate it very much.You can replicate this build to your own satisfaction by running
nix build
from the repo's root or runningnix build github:danthony28/FUTO.MDNS/flake-futo-mdns
from pretty much anywhere and digging through theresult
symlink. My intentions are to use this derivation as-is in the waydotnet build
,dotnet publish
, etc. expect in the flake.nix for Grayjay.ClientServer; ideally straight from nixpkgs but it's just a flake for now.I'll commit the lockfile once everything is verified to be working as dotnet expects on Grayjay.ClientServer (not just as I expect).
Note
To the maintainers
I'll be following the "branch stacking" convention for these flakes, so it may be more convenient to merge a different branch, which should be mentioned below. I'll do my best to specifically comment when a branch shouldn't be merged into
master
(this is usually because it will cause messy conflicts down the road).Warning
alejandra.toml
support is experimental!Alejandra, my formatter of choice, only added support for
alejandra.toml
in v3.1.0. All branches of nixpkgs are up-to-date (i.e., package v3.1.0 of alejandra) but your system's software repository may differ. You can runalejandra --version
to be sure.