<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="">Thanks for the stats Honza, that matches my manual estimates.<div class=""><br class=""></div><div class="">We probably can't expect to explicitly notify clients of API changes, my expectation is that what we should typically do is try and ensure that API changes come with as helpful a diagnostic as possible. Before Swift 3 is complete, though, my opinion is that the manifest is "unstable" (even though we haven't changed it much) and can expect clients to update on their own if/when they try a new version of the package manager.</div><div class=""><br class=""></div><div class="">After Swift 3 is complete, we are still going to need to change the manifest format, but we should try to be more careful and ensure API changes come with deprecation warnings etc.</div><div class=""><br class=""></div><div class=""> - Daniel</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Jul 13, 2016, at 1:25 AM, Honza Dvorsky <<a href="mailto:jan.dvorsky@me.com" class="">jan.dvorsky@me.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">I agree that the name should be required. In order to better understand the impact on existing packages, I pulled some stats for how many packages currently don't explicitly specify their name in their manifest - 119 out of 2222, which is about 5 % of all packages I crawled from GitHub. The list of their names is attached to this email, so that we could potentially write a script to create an issue on their repos to notify them of this coming change.</div><div class=""><br class=""></div><div class="">Honza</div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Wed, Jul 13, 2016 at 2:32 AM Daniel Dunbar via swift-build-dev <<a href="mailto:swift-build-dev@swift.org" class="">swift-build-dev@swift.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We currently allow:<br class="">
```<br class="">
let package = Package() // Note no name here<br class="">
```<br class="">
in a package manifest, but this turns out to be both problematic and rarely used.<br class="">
<br class="">
I intend to move to making this required, here:<br class="">
<a href="https://github.com/apple/swift-package-manager/pull/486" rel="noreferrer" target="_blank" class="">https://github.com/apple/swift-package-manager/pull/486</a><br class="">
but wanted to run it past the list in case anyone has an objection.<br class="">
<br class="">
- Daniel<br class="">
<br class="">
_______________________________________________<br class="">
swift-build-dev mailing list<br class="">
<a href="mailto:swift-build-dev@swift.org" target="_blank" class="">swift-build-dev@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-build-dev" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-build-dev</a><br class="">
</blockquote></div></div>
<span id="cid:155e3582416562868e51"><NamelessPackages.json></span></div></blockquote></div><br class=""></div></body></html>