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

[SR-9382] Allow selection of a specific versioned package manifest #4742

Closed
glessard opened this issue Nov 30, 2018 · 4 comments
Closed

[SR-9382] Allow selection of a specific versioned package manifest #4742

glessard opened this issue Nov 30, 2018 · 4 comments

Comments

@glessard
Copy link

Previous ID SR-9382
Radar rdar://problem/46189034
Original Reporter @glessard
Type Improvement
Status Resolved
Resolution Done
Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels Improvement
Assignee None
Priority Medium

md5: 0bb0bfd7b3747290341cf21cd0e1619c

Issue Description:

If I have versioned package manifests such as

Package.swift // swift-tools-version:4.2
Package@swift-3.1.swift
Package@swift-4.swift

There is currently no way to make `swift test` in previous-version compatibility mode so as to test behaviour in every case – this is obviously useful for a library that might be included by another package that itself still builds using a compatibility mode.

The workaround is obviously to manipulate and rename package manifests, but that is less than desirable.

@neonichu
Copy link
Member

neonichu commented Dec 4, 2018

@swift-ci create

@ankitspd
Copy link
Member

ankitspd commented Jan 2, 2019

#1919

@glessard
Copy link
Author

Forgive my denseness, but I don't see what the solution was here.

I still can't figure out how to make the swift 5 tools run my test in 4.2 mode without juggling manifests. I really thought the following (or something equivalent) would become a possibility:

swift test ``-swift-version 4.2

@glessard
Copy link
Author

After all this time, I tried the terrible:

swift test -Xswiftc -swift-version -Xswiftc 4.2

And that's the thing that works.

Ouch!

@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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants