Re: [swift-evolution] [Draft] Package Manager Revised Dependency Resolution

+ 1 > On 02 May 2017, at 00:00, Martin Waitz via swift-evolution > wrote: > > Hello, > > Many of the listed package managers are for interpreted languages. > So after fetching all dependencies, your package is completely usable. It is > „installed locally“. > But

Re: [swift-evolution] [Draft] Package Manager Revised Dependency Resolution

Hello, Many of the listed package managers are for interpreted languages. So after fetching all dependencies, your package is completely usable. It is „installed locally“. But Swift packages have to be compiled. You have to build them to be able to use them. For me, ‚install' comes after

Re: [swift-evolution] [Draft] Package Manager Revised Dependency Resolution

> On 1 May 2017, at 00:46, Jon Shier wrote: > > `install` only sounds like it should install things in the system if > that’s the only type of manager you’ve ever used. If I’ve only ever used > brew, of course I’ll assume that every other thing that calls itself a >

Re: [swift-evolution] [Draft] Package Manager Revised Dependency Resolution

`install` only sounds like it should install things in the system if that’s the only type of manager you’ve ever used. If I’ve only ever used brew, of course I’ll assume that every other thing that calls itself a package manager will operate similarly. Thankfully, people learn quickly

Re: [swift-evolution] [Draft] Package Manager Revised Dependency Resolution

Thanks for the feedback, David, and apologies for the slow reply. My biggest reservation with the word "install" is that it really sounds like it should install things into the system, or another shareable location, instead of fetching dependencies into the dependency location for a single

Re: [swift-evolution] [Draft] Package Manager Revised Dependency Resolution

This new proposal is great, I'm all in. On Wed, Apr 26, 2017, at 17:25, Rick Ballard via swift-evolution wrote:> Hi all, > > We have a proposal we'd like feedback on to revise how Swift Package > Manager dependency resolution, updating, and pinning works. These > changes weren't planned in the

Re: [swift-evolution] [Draft] Package Manager Revised Dependency Resolution

Hello Rick, thanks for the great proposal! Strong +1 from me :-) — Martin > Am 27.04.2017 um 02:25 schrieb Rick Ballard via swift-evolution > : > > Hi all, > > We have a proposal we'd like feedback on to revise how Swift Package Manager > dependency resolution,

Re: [swift-evolution] [Draft] Package Manager Revised Dependency Resolution

Very happy about this proposal as the pinning feature was un-necessarily complicated and because SwiftPM will now work like many other package managers out there: users won't be surprised. By the way, why wasn't resolve called install instead, mirroring the terminology used everywhere else? It

[swift-evolution] [Draft] Package Manager Revised Dependency Resolution

Hi all, We have a proposal we'd like feedback on to revise how Swift Package Manager dependency resolution, updating, and pinning works. These changes weren't planned in the roadmap we published a few months ago, but it's become clear since then that we have some holes in our dependency