Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
more docs
  • Loading branch information
matthid committed Aug 26, 2017
commit 27da527fa4d3e27aaf8d50c86bc15c86f44a26bc
16 changes: 14 additions & 2 deletions docs/content/dependencies-file.md
Original file line number Diff line number Diff line change
Expand Up @@ -157,8 +157,19 @@ If you change the target framework of the projects then you need to run

### Disable packages folder

You can opt-out of generating the `packages` folder by using the `storage` option:
With the net netcore release and the switch to provide more and more netstandard-only packages
the Paket team noticed an dramatic increase of the well known "packages" folder.
Historically one way was to tell Paket that you only want to compile for `framework: net45`.
However, this doesn't prevent netstandard dependencies in all situations.
On the other side more features are provided by Paket and the packages folder has become more and more redundant:
- Load scripts can reference the files in the global cache
- csproj/fsproj files can references files in the global cache
- netcore project files don't require any explicit dll-references
Therefore, the paket team decided to make the "packages" folder opt-out.

> This feature is currently considered beta

You can opt-out of generating the `packages` folder by using the `storage` option:

```paket
// Do not extract into the "packages" folder but use a globally shared directory
Expand All @@ -168,7 +179,8 @@ source https://nuget.org/api/v2
nuget jQuery
```

The storage option may be overriden by packages.
The storage option may be overriden by packages.
However, the behavior is undefined and may change (please open an issue if you depend on the current behavior or we break you).

### Controlling whether content files should be copied to the project

Expand Down
4 changes: 4 additions & 0 deletions docs/content/paket-and-dotnet-cli.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,10 @@ allows you to use specialized NuGet packages that provide `dotnet` CLI tools.

CLI tools are only available for .NET SDK-based projects.

> Consider setting `storage: none` in your dependencies file for the relevant groups to mirror NuGet behavior and
> not copy all dependencies to the packages folder. This will keep your repository folder small and clean.
> Please read the relevant section of the [`paket.dependencies` file](dependencies-file.html) documentation.

### Installing dependencies

Install all required packages with:
Expand Down