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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paket lock file & doc #980
Conversation
generated with command: `.paket\paket.exe install`
oof that's a lot of dependencies. How many of them end up in the zip?
馃檱 thank you! is there a way to make one of the CI builds check that the packet.lock file that's checked in is correct? Like maybe after restoring packages it could check if the file is different? |
none. I have tested the generated package and it works well without. But I must have taken the time to test it :(
No, I don't see a reliable way to do it. The lock file define the dependencies version calculated at one time (and thus validated as "it works" by the developper). The restore will be done based on this file. The only way to recompute the lock file is to delete it and let paket recreate it. And then we could compare it with the one committed. But everytime a dependency will upgrade (thus we have an outdated package), we will have a warning/error. The thing your are imagining is generaly done by not committing the lock file, and the lock will be regenerated at each build but that's not generaly what is expected because that's not us anymore that handle version upgrading of dependencies.... |
and undo the |
ah. I was imagining that when CI runs paket that it could then do
Cool. Would it be worth adding a comment to 馃憤 on this PR |
I have added the links. Feel free to merge... |
paket.lock
forgotten in Feature/fix changesets comments policy error聽#979GitTfs.Vs2015.csproj
file when a nuget package is updated or a new one is added!) Which is not quite easy to handle (even if its better with paket than with pure nuget)....PS: The new TFS nuget packages add A LOT more dependencies than the previous ones (seems partly due to donet core), and that begin to worry me 馃槩
I don't know if there is a solution for that....(but that's for another PR)