> Can you take a look at:
> ... and see if you feel it would meet your needs?
Thanks, it looks great :)
One minor thing, I am not sure about the
.Package(url: “…”, subpackage: ..., …)
syntax, maybe the subpackage name should be included in the url? I am not sure…
-g.
__
> On Nov 3, 2016, at 2:06 PM, Erica Sadun via swift-users
> wrote:
>
> I want less of a monorepo than an ability to build a group of orthogonal
> elements into a single repo so I don't have to create a separate repo for
> every single Swift library I build, especially when there are logical
(+ swift-build-dev)
Hi Georgios,
This is a very timely question, because I have been working on a proposal for
solving exactly this problem.
Can you take a look at:
https://github.com/ddunbar/swift-evolution/blob/multi-package-repos/proposals/-swiftpm-multi-package-repos.md
and see if yo
> It would be good if you can explainyour requirements/features/floware you
> looking for.
Well the flow is simple, just put all your packages in one root repository. I
guess, SPM could be updated to allow
linking to a local dependency by file path, not only by Git tag.
Actually this feature w
I want less of a monorepo than an ability to build a group of orthogonal
elements into a single repo so I don't have to create a separate repo for every
single Swift library I build, especially when there are logical relationships
between subfolders and partial incorporation into builds For exa
+swift-build-dev
Not right now but we're considering adding support for multiple packages in
a repository. It would be good if you can explain your
requirements/features/flow are you looking for.
On Friday 4 November 2016, Georgios Moschovitis via swift-users <
swift-users@swift.org> wrote:
> Th
The Swift Package Manager is a great addition to the Swift programmer's
toolbelt and in general I like the integration with Git.
However, since SPM promotes a separate Git repo per package and actually
leverages Git tags to resolve dependency versions, I am wondering if it's
possible to use the
