Open kirinnee opened 3 years ago
I marked this as stale due to inactivity. → More info
Not stale, just ran into this with Terminal.Gui
. Send help!
I ran into this same issue just now, and I think I managed to figure out a solution:
postUnpack = ''
chmod -R +r .
'';
This makes the unpacked directory have permission to read, thus letting it copy properly.
How do you allow it to be used as a tool?
Not sure about that yet. (I'm relatively new to the dotnet ecosystem overall, so I'm not sure how far my knowledge would go to making that happen lol). I got a bit farther in trying to use buildDotnetModule
, which could at least try to build it, but not sure how that would apply to fetchNuGet
. (In my case, I've been trying to package https://github.com/belav/csharpier)
I think when you opened this issue it was still a work-in-progress, but fetchNuGet
currently works fine for its intended purpose: in auto-generated Nix expressions to be imported as e.g. buildDotnetModule { nugetDeps = ./deps.nix; }
, as documented here (official).
However, that's only for normal NuGet packages. For dotnetsay
and other .NET tools, you can add them to a project in the usual way: dotnet new tool-manifest
if absent, then dotnet tool install dotnetsay
. For --global
, see #216285.
Issue description
I'm fairly new to Nix, so I apologise if the question is simple.
I would like to know how to use fetchNuGet, but it seems to have read permission problems.
I have tried installing with
--daemon
and turningsandbox = false
, and still have this problems.Steps to reproduce
default.nix
I'm trying to package a dotnet demo CLI
dotnetsay
(like hello world) fordotnet
's global tool.Logs:
Technical details
I've replicated this in ubuntu and alpine (within container) and osx.
Some guidance on how I can debug this, or track down the problem will be appreciated. I tried to track on nixpkgs fetchNuGet and buildDotnetPackage, but I'm not too sure how to breakdown/debug it.