Hello,
Firstly, I want to mention I have been using Paket for a little while now and love the software.
Here is my problem,
I have 3 projects (A, B, C) where
B depends on (A 2.0 prerelease)
C depends on (B 1.0 prerelease)
A, B are libraries and are shipped in their respective nuget packages created using Paket. We are using SemVer with prerelease tags. (using GitFlow)
Nuget packages for A are usually named something like "A 1.0-unstable0021"
Projects B resolve correctly its dependency to A on "paket update". When we use "paket pack" for package B, it creates the following nuget dependencies,
A( = 1.0.0-prerelease)
The thing is, when we try to "paket update" C, it cannot resolve A. I think he is is looking for a package versionned exactly "1.0.0-prerelease".
(The problem also applies to prerelease ranges (~>, <, >, etc.))
I don't quite know how to solve this problem. Maybe it is a comprehension issue, but if it is not, I'd be happy to contribute.
Hello,
Firstly, I want to mention I have been using Paket for a little while now and love the software.
Here is my problem,
I have 3 projects (A, B, C) where
B depends on (A 2.0 prerelease)
C depends on (B 1.0 prerelease)
A, B are libraries and are shipped in their respective nuget packages created using Paket. We are using SemVer with prerelease tags. (using GitFlow)
Nuget packages for A are usually named something like "A 1.0-unstable0021"
Projects B resolve correctly its dependency to A on "paket update". When we use "paket pack" for package B, it creates the following nuget dependencies,
A( = 1.0.0-prerelease)
The thing is, when we try to "paket update" C, it cannot resolve A. I think he is is looking for a package versionned exactly "1.0.0-prerelease".
(The problem also applies to prerelease ranges (~>, <, >, etc.))
I don't quite know how to solve this problem. Maybe it is a comprehension issue, but if it is not, I'd be happy to contribute.