dev/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

doc: Update note under buildDotnetModule to reflect actual behaviour

Browse Source
This commit is contained in:
YoshiRulz 2024-06-25 00:15:29 +10:00
parent 3da824d0b1
commit 5c3f56c32a
No known key found for this signature in database
GPG Key ID: C4DE31C245353FB7
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/languages-frameworks/dotnet.section.md
View File

@ -142,9 +142,7 @@ in buildDotnetModule rec {
src = ./.; src = ./.;
projectFile = "src/project.sln"; projectFile = "src/project.sln";
# File generated with `nix-build -A package.passthru.fetch-deps`. nugetDeps = ./deps.nix; # see "Generating and updating NuGet dependencies" section for details
# To run fetch-deps when this file does not yet exist, set nugetDeps to null
nugetDeps = ./deps.nix;
projectReferences = [ referencedProject ]; # `referencedProject` must contain `nupkg` in the folder structure. projectReferences = [ referencedProject ]; # `referencedProject` must contain `nupkg` in the folder structure.
@ -220,6 +218,12 @@ buildDotnetGlobalTool {
``` ```
## Generating and updating NuGet dependencies {#generating-and-updating-nuget-dependencies} ## Generating and updating NuGet dependencies {#generating-and-updating-nuget-dependencies}
When writing a new expression, you can use the generated `fetch-deps` script to initialise the lockfile.
After creating a blank `deps.nix` and pointing `nugetDeps` to it,
build the script with `nix-build -A package.fetch-deps` and then run the result.
(When the root attr is your package, it's simply `nix-build -A fetch-deps`.)
There is also a manual method:
First, restore the packages to the `out` directory, ensure you have cloned First, restore the packages to the `out` directory, ensure you have cloned
the upstream repository and you are inside it. the upstream repository and you are inside it.
@ -255,6 +259,5 @@ Finally, you move the `deps.nix` file to the appropriate location to be used by
If you ever need to update the dependencies of a package, you instead do If you ever need to update the dependencies of a package, you instead do
* `nix-build -A package.fetch-deps` to generate the update script for `package` * `nix-build -A package.fetch-deps` to generate the update script for `package`
* Run `./result deps.nix` to regenerate the lockfile to `deps.nix`, keep in mind if a location isn't provided, it will write to a temporary path instead * Run `./result` to regenerate the lockfile to the path passed for `nugetDeps` (keep in mind if it can't be resolved to a local path, the script will write to `$1` or a temporary path instead)
* Finally, move the file where needed and look at its contents to confirm it has updated the dependencies. * Finally, ensure the correct file was written and the derivation can be built.