[swift-evolution] [swift-build-dev] [Review] SE-0085: Package Manager Command Names

[Jean-Daniel Dupas]

> Le 10 mai 2016 à 18:38, Rick Ballard via swift-evolution <swift-evolution at swift.org> a écrit :
> 
> 
>> On May 10, 2016, at 8:49 AM, Matthew Johnson via swift-build-dev <swift-build-dev at swift.org <mailto:swift-build-dev at swift.org>> wrote:
>> 
>> 
>>> On May 10, 2016, at 2:19 AM, Dan Appel via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>> 
>>> +1 to `swift package` being a little too verbose. However, I like the alternative `swift pm`/`swiftpm` (as noted in the proposal) even less. I have already been referring to the package manager as SPM, so IMO that name does not lose out on any clarity while also allowing it to be terse enough for every day use. 
>>> 
>>> I would not be against having both `spm` and `swift package` as Honza suggested.
>> 
>> + 1 to the proposal in general and also to adding the `spm` alias.
> 
> Question for those of you who are advocating for a "spm" alias: Do you have a strong argument / preference for "spm" vs "swiftpm"? Personally I have been abbreviating the project as "swiftpm" and not "spm" when I talk about it, and have been trying to push that as the preferred abbreviation. "spm" is a few less keystrokes, but is a much more generic, less googleable name; out of context, it's impossible to know what it refers to. Once the project gets enough mindshare, like "npm" has, that might be less of an issue, but I still personally prefer the more descriptive "swiftpm". Thoughts?

I prefer swiftpm because I have enough three letters tools on my machine that I never know what they do without having to open the man page. Having an explicit name will reduce the chance of conflict with other tools and greatly simplify its discovery.

And for those who think this is a too long name, creating a shorter alias in any shell is relatively easy.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160510/0e0df833/attachment.html>