[swift-users] Monorepo workflow using SPM

Erica Sadun erica at ericasadun.com
Thu Nov 3 16:06:33 CDT 2016

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 example, I'm messing with core graphics geometry right now. I have basic types & extensions, some experimental stuff, and other misc things for (for example) doing playground visualization support. Rather than over-conditionalize my code, I'd rather conditionalize the package, so that everything pulls, compiles, and works fine on, say, a macOS build but bits that don't belong (iOS playground visualization support) can be omitted from a specific configuration *for* *that* *repo* instead of me having to make really ugly code conditions in files which are intended specifically for known targets and may be excluded from package builds because of their intended targets.

-- E

> On Nov 3, 2016, at 2:31 PM, Ankit Agarwal via swift-users <swift-users at swift.org> wrote:
> +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 at swift.org <mailto:swift-users at swift.org>> wrote:
> 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 popular(?) 'monorepo' workflow with SPM. 
> thanks,
> -g.
> -- 
> Ankit
> _______________________________________________
> swift-users mailing list
> swift-users at swift.org
> https://lists.swift.org/mailman/listinfo/swift-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20161103/0ba2dc05/attachment.html>

More information about the swift-users mailing list