You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a two-stage build system, where the build dependencies are handled separately, under nested directory, and allow to specify custom paket.dependencies for the projects' build tools, incl. Paket itself,
which is then used to download the actual projects' packages.
As we have long-term issues with NuGet caches, when build agent temporarily loses connectivity to repository, or the repository fails, and an empty or damaged NuPkg was downloaded, we simply call paket clear-cache from critical builds to update/restore from scratch.
Recent change to clear-cache -- deleting content of packages under current directory -- results in either: 1/ deleting the build scripts and ending with error as it tries to delete itself, or 2/ deleting all of the project's locked packages, making update much longer.
Repro steps
Call clear-cache to reset the global NuGet cache from any directory with paket dependencies/packages.
Expected behavior
Paket clear-cache should keep the original behavior and only delete the global cache/s.
New verb or switch (like --local, --packages or something descriptive) should be introduced to delete the packages directory content.
Known workarounds
Change current directory to a temp path without packages and then jump back to call other Paket commands.
The text was updated successfully, but these errors were encountered:
Description
We have a two-stage build system, where the build dependencies are handled separately, under nested directory, and allow to specify custom
paket.dependencies
for the projects' build tools, incl. Paket itself,which is then used to download the actual projects' packages.
As we have long-term issues with NuGet caches, when build agent temporarily loses connectivity to repository, or the repository fails, and an empty or damaged NuPkg was downloaded, we simply call
paket clear-cache
from critical builds to update/restore from scratch.Recent change to
clear-cache
-- deleting content ofpackages
under current directory -- results in either: 1/ deleting the build scripts and ending with error as it tries to delete itself, or 2/ deleting all of the project's locked packages, making update much longer.Repro steps
Call
clear-cache
to reset the global NuGet cache from any directory with paket dependencies/packages.Expected behavior
Paket
clear-cache
should keep the original behavior and only delete the global cache/s.New verb or switch (like
--local
,--packages
or something descriptive) should be introduced to delete thepackages
directory content.Known workarounds
Change current directory to a temp path without packages and then jump back to call other Paket commands.
The text was updated successfully, but these errors were encountered: