Skip to content
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

Jump to bottom

[SR-965] How to depend on a specified Pre-release version of package with the Swift Package Manager #5381

Closed
swift-ci opened this issue Mar 17, 2016 · 4 comments
Closed

[SR-965] How to depend on a specified Pre-release version of package with the Swift Package Manager #5381

swift-ci opened this issue Mar 17, 2016 · 4 comments

Comments

@swift-ci
Copy link
Contributor

Previous ID SR-965
Radar None
Original Reporter Martha (JIRA User)
Type Improvement
Status Resolved
Resolution Duplicate
Environment

OS X 10.11.3（15D21）

Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Improvement
Assignee None
Priority Medium

md5: 9a26d5a4cdb3297bd97b1dc83f6fe3c5

duplicates:

  • SR-1039 Fetch a dependency with a specified Pre-release version

Issue Description:

  • Apple Platforms

  • Apple Swift version 3.0-dev (LLVM b361b0fc05, Clang 11493b0f62, Swift 24a0c3de75)

Himotoki package has tags 2.0.0-beta.1 and 2.0.0-beta.2, and I intend to depend on 2.0.0-beta.1.

If I implement the following:

import PackageDescription

let package = Package(
    name: "Example",
    dependencies: [
        .Package(url: "https://github.com/ikesyo/Himotoki.git", Version(2, 0, 0, prereleaseIdentifiers: ["beta", "1"]))
    ]
)

Then, I expect 2.0.0-beta.1 is downloaded, but 2.0.0-beta.2 is downloaded because the resulting range is 2.0.0-beta.1..<2.0.1.
I think it's unexpected behavior.

I'm sorry if I got the wrong idea.
@swift-ci
Copy link
Contributor Author

Comment by Kostiantyn Koval (JIRA)

There is bug in swiftPM when fetching a package with `prereleaseIdentifiers `.
In your Manifest you specify have specified a specific version -
Version(2, 0, 0, prereleaseIdentifiers: ["beta", "1"]). It's 2.0.0-beta.1 and it should be fetched.

There is an open discussion how this issue should be fixed.
#179

@swift-ci
Copy link
Contributor Author

Comment by Satoshi Hachiya (JIRA)

Hi, kkoval (JIRA User).
Thank you for teaching me!
It seems the same thing has discussed there.
I hadn't watched it thorouoghly enough, I'm sorry.

@swift-ci
Copy link
Contributor Author

Comment by Kostiantyn Koval (JIRA)

Thanks for taking your time and reporting the bug. It helps improving the swiftpm.

@abertelrud
Copy link
Contributor

If this is still not working correctly, but it is expected to, then it is a candidate for a Swift 3 update fix.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@swift-ci @abertelrud