Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Paket Add should call Install, and not Update

See original GitHub issue

I believe that calling paket add currently calls paket update after adding the package to the dependencies file. I believe that this behaviour should be replaced with calling paket install.

Currently, calling paket add currently will cause the lock file to silently update not just the changes caused by adding the new package but update the entire graph.

Issue Analytics

State:
Created 4 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

forkicommented, Nov 14, 2019

OMG I think I found the bug. WTF!!?

0reactions

isaacabrahamcommented, Nov 14, 2019

Hoppla 😃 So, I can confirm that the latest Paket doesn’t do this any more 😃

Top Results From Across the Web

Confusion between "paket install" and "paket update" #848

Proposed solution: My intuition is that paket install should really be called paket update --pin-unchanged , because this is what it really does ......

Learn how to use paket

The most frequently used Paket commands are: paket install - Run this after adding or removing packages from the paket.dependencies file. It will...

paket update

Updating all packages ... If you do not specify a package, then all packages from paket.dependencies are updated. ... First, the current paket.lock...

Why can't I add packages with Paket?

I tried to add XUnit from the command line. A line with nuget xunit appeared in the paket.dependencies file. But there is no...

Getting Started with Paket – Part 1 - The Cockney Coder

Json, and call paket install. This time, we won't need to add anything to the dependencies file, since Newtonsoft.