<div dir="ltr">+1 to spm or swiftpm (in that order)<div>As a swiftpm user I would imagine it works like :</div><div>spm -> builds</div><div>spm test -> runs tests</div><div>spm init -> new project</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 10, 2016 at 1:12 PM, Rob Allen via swift-build-dev <span dir="ltr"><<a href="mailto:swift-build-dev@swift.org" target="_blank">swift-build-dev@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On 9 May 2016, at 23:05, Daniel Dunbar via swift-build-dev <<a href="mailto:swift-build-dev@swift.org">swift-build-dev@swift.org</a>> wrote:<br>
><br>
> Hello Swift community,<br>
><br>
> The review of "SE-0085: Package Manager Command Names" begins now and runs through May 12. The proposal is available here:<br>
><br>
> <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0085-package-manager-command-name.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0085-package-manager-command-name.md</a><br>
><br>
<br>
<br>
</span>Hi,<br>
<br>
I like this proposal a lot as the functionality switches to swift build feel like bolt-ons and we're already up to four of these, so it's probably not sustainable long term as SPM evolves.<br>
<br>
I'm not totally sold on `swift package` as the new command though as "package" is an imperative verb like "build" or "test" and implies that if I run it, then it will generate a "package" whereas it will actually do nothing as an additional switch will be required. This requirement to always take a second sub-command makes it different from `swift build` and `swift test` too. Are there any commands to `swift` current that require a sub-command to work?<br>
<br>
Maybe it would be better for the package manager to be separate from the swift command? If separate, the obvious name would be `spm` as that's what we all call it anyway. `swiftpm` as noted in the alternatives section would also work. If we have to have it as a subcommand of `swift` then, I'd rather have `swift pm` as that way the command is obviously the third word in `swift pm init`.<br>
<br>
<br>
I would also prefer to remove the subcommand flags from `swift build` at the same time as when this change lands rather than delayed. That way it all happens in one go rather than as two stages which means only one announcement point is needed. The band-aid has to be ripped off at some point as `swift build --init` won't work in v3, so better for it to be gone before new developers find it during when downloading the preview released and then have to learn the new way.<br>
<br>
<br>
Finally, having raised my concerns, I'd like to emphasise that I'm very much in favour of this proposal and would prefer it to be accepted as-is rather than be rejected as I really dislike the current sub-command flags to `swift build`!<br>
<br>
<br>
Regards,<br>
<br>
Rob...<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
swift-build-dev mailing list<br>
<a href="mailto:swift-build-dev@swift.org">swift-build-dev@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-build-dev" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-build-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Ankit<br><br></div>
</div>