New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change in paket clear-cache results in self-destruct #3049

Closed
viktor-svub opened this Issue Feb 14, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@viktor-svub
Contributor

viktor-svub commented Feb 14, 2018

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 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.

@forki forki closed this in de149d9 Feb 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment