<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 3, 2016, at 2:06 PM, Erica Sadun via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">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.</div></div></blockquote><div><br class=""></div>Can you explain the interaction between conditional compilation and monorepo / multi-package repos? They seem somewhat orthogonal to me.</div><div><br class=""></div><div> - Daniel</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">-- E</div><div class=""><br class=""><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Nov 3, 2016, at 2:31 PM, Ankit Agarwal via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">+swift-build-dev<div class=""><br class=""></div><div class="">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.<br class=""><br class="">On Friday 4 November 2016, Georgios Moschovitis via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo;background-color:rgb(255,255,255)" class=""><span class="">The Swift Package Manager is a great addition to the Swift programmer's toolbelt and in general </span>I like the integration with Git.</div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo;background-color:rgb(255,255,255);min-height:13px" class=""><span class=""></span><br class=""></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo;background-color:rgb(255,255,255)" class=""><span class="">However, since SPM promotes a separate Git repo per package and actually leverages Git tags to </span>resolve dependency versions, I am wondering if it's possible to use the popular(?) 'monorepo' workflow with SPM. </div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo;background-color:rgb(255,255,255);min-height:13px" class=""><span class=""></span><br class=""></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo;background-color:rgb(255,255,255)" class=""><span class="">thanks,</span></div><div style="margin:0px;font-size:11px;line-height:normal;font-family:Menlo;background-color:rgb(255,255,255)" class=""><span class="">-g.</span></div></div></blockquote></div><br class=""><br class="">-- <br class="">Ankit<br class=""><br class=""><br class="">
_______________________________________________<br class="">swift-users mailing list<br class=""><a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-users" class="">https://lists.swift.org/mailman/listinfo/swift-users</a><br class=""></div></blockquote></div><br class=""></div></div></div>_______________________________________________<br class="">swift-users mailing list<br class=""><a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-users<br class=""></div></blockquote></div><br class=""></body></html>