<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">> Proposal link:<br class="">>> <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0158-package-manager-manifest-api-redesign.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0158-package-manager-manifest-api-redesign.md</a><div class=""><br class=""></div><div class=""><blockquote type="cite" class="">On Mar 9, 2017, at 2:30 PM, Karl Wagner <<a href="mailto:razielim@gmail.com" class="">razielim@gmail.com</a>> wrote:</blockquote></div><div class=""><blockquote type="cite" class=""><div class=""><blockquote type="cite" class=""><div class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="">* Is the problem being addressed significant enough to warrant a change to the Swift Package Manager?<br class=""></div></div></div></blockquote><div class=""><br class=""></div><div class="">Not really. The package manifest API has lots of serious deficiencies and this proposal shuffles a couple of names around. Not sure it’s really worth the hassle, to be honest. It’s certainly very far from a “redesign”!</div></div></blockquote></div><div class=""><br class=""></div><div class="">Hi Karl,</div><div class=""><br class=""></div><div class="">Would you mind expanding on the other deficiencies that you see in this API?</div><div class=""><br class=""></div><div class="">Thanks,</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- Rick</div><div class=""><br class=""></div></body></html>