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-3951] Multi-Package Repository Support #5108
Comments
There is a draft evolution proposal in progress at https://github.com/ddunbar/swift-evolution/blob/multi-package-repos/proposals/NNNN-swiftpm-multi-package-repos.md |
@swift-ci create |
Comment by Mitch Denny (JIRA) Is there any ongoing conversation about this issue? We filed this issue yesterday which is related: https://bugs.swift.org/browse/SR-12266 Basically we have a mono-repo that we want to ship multiple packages from. These packages have some internal dependencies but we want to be able to ship each package at its own cadence. Our SDK represented by the group of packages covers a fairly large surface area, and it doesn't make sense to do version bumps of all packages when just one has changed (a major version bump would be super confusing if there were no changes for example). Basically what we are asking for is more affordances for mono-repositories. |
+1 from the Firebase folks 🙂 we currently ship >25 CocoaPods from our repo (https://github.com/Firebase/firebase-ios-sdk). We would simplify that with SwiftPM but still would like to have 5-6 different packages available from that repo. I imagine there could be extra complexity with something like this considering there's likely Xcode UI changes involved as well. |
Additional Detail from JIRA
md5: 51bfd5837ab7785231c5ec11c3fc9c8d
is duplicated by:
Issue Description:
Currently the package manager requires that each package live at the root of a Git repository. This means that you can't store multiple packages in the same repository, or develop packages which locate each other in a filesystem-relative manner without relying on Git. We need a proposal for how we would like to support this.
The text was updated successfully, but these errors were encountered: