Re: [swift-evolution] [swift-build-dev] Proposal: Package Manager Version Pinning

2016-10-14 Thread Rob Allen via swift-evolution
> On 14 Oct 2016, at 18:55, Daniel Dunbar via swift-build-dev > wrote: > >> On Oct 14, 2016, at 9:43 AM, Alexis via swift-evolution >> mailto:swift-evolution@swift.org>> wrote: >> >>> On Oct 14, 2016, at 2:01 AM, Ankit Aggarwal via swift-evolution >>> mailto:swift-evolution@swift.org>> wrote

Re: [swift-evolution] [swift-build-dev] Proposal: Package Manager Version Pinning

2016-10-14 Thread Rob Allen via swift-evolution
Hi, As noted by others, the standard extension for this file .lock, so I would prefer to keep that convention. As I would never want my CI or any random team member to build a different package to what I've developed and tested already, I will always want Package.lock to exist. It's much easie

Re: [swift-evolution] [Review] SE-0135: Package Manager Support for Differentiating Packages by Swift version

2016-08-04 Thread Rob Allen via swift-evolution
I appreciate that I'm late on this, but I'm on vacation. > On 29 Jul 2016, at 20:36, Daniel Dunbar via swift-evolution > wrote: > > Hello Swift community, > > The review of "SE-0135: Package Manager Support for Differentiating Packages > by Swift version" begins now and runs through August

Re: [swift-evolution] [Review] SE-0084: Allow trailing commas in parameter lists and tuples

2016-05-13 Thread Rob Allen via swift-evolution
> On 13 May 2016, at 07:22, Vladimir.S via swift-evolution > wrote: > > It seems like all problems could be solved by allowing line-break instead of > comma in list: For what it's worth, I'm very much in favour of this idea of allowing line breaks instead of commas in lists. I'm neutral on

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

2016-05-10 Thread Rob Allen via swift-evolution
> On 10 May 2016, at 16:38, Daniel Dunbar wrote: > > >> On May 10, 2016, at 12:42 AM, Rob Allen via swift-build-dev >> wrote: >> >> 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

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

2016-05-10 Thread Rob Allen via swift-evolution
> On 10 May 2016, at 16:38, Daniel Dunbar wrote: > > >> On May 10, 2016, at 12:42 AM, Rob Allen via swift-build-dev >> wrote: >> >> 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 i

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

2016-05-10 Thread Rob Allen via swift-evolution
> On 10 May 2016, at 17:38, Rick Ballard via swift-evolution > wrote: > > 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 ta

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

2016-05-10 Thread Rob Allen via swift-evolution
> On 10 May 2016, at 10:04, Honza Dvorsky wrote: > > I agree with Rob and Ankit, with one detail: I'd expect `spm` to print the > help section, instead of building (just like npm, nvm, gem, pod etc). Agreed. We have `swift build` for building. Regards, Rob... _

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

2016-05-10 Thread Rob Allen via swift-evolution
> On 9 May 2016, at 23:05, Daniel Dunbar via swift-build-dev > wrote: > > Hello Swift community, > > The review of "SE-0085: Package Manager Command Names" begins now and runs > through May 12. The proposal is available here: > > > https://github.com/apple/swift-evolution/blob/master