Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
exactly-this-operator does not seem to work #2777
FsPickler 4.0 was just just released.
Unfortunately, a few of my other dependencies have a hard check
My current strategy (lets see if it works) is to just pin everything to their latest versions with
Instead I would want to be able to specify
then it should resolve the latest version of each of these packages, ignoring conflicting version ranges.
O_o Am 18.09.2017 12:40 schrieb "Lukas Rieger" <firstname.lastname@example.org>:…
Description FsPickler 4.0 was just just released <https://www.nuget.org/packages/FsPickler/4.0.0>. Unfortunately, a few of my other dependencies have a hard check < 4.0: [image: image] <https://user-images.githubusercontent.com/4236651/30538405-256bf166-9c6e-11e7-9978-3910fe4e7647.png> [image: image] <https://user-images.githubusercontent.com/4236651/30538418-32329a8a-9c6e-11e7-861a-871b6fac1ef2.png> My current strategy (lets see if it works) is to just pin everything to their latest versions with ==. Unfortunately, this means that paket update becomes kind of useless. Instead I would want to be able to specify nuget FsPickler == latest MBrace.Thespian == latest Vagabond == latest ... then it should resolve the latest version of each of these packages, ignoring conflicting version ranges. Transitives should still be resolved normally, I may need to pin some more packages. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2777>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNMkeecLVn-jZzr-eJGJ7SoDklGhRks5sjkiugaJpZM4Pat4E> .
Also, the take-exactly-this operator seems broken:
Investigating this issues further, I have the impression, the problem is related to the number of packagings that require a "conflicting" version (sorry for caps, lots of code / console following).
Stripping down @0x53A sample:
seems to work:
Adding another dependency that results in the same conflict breaks the exactly-this-operator: