Swift Package Manager tag about swifter

[cwagdev]

+1 not sure if that's the cause for my issue but I am seeing the following

Cloning Packages/swifter
swift-build: The dependency graph could not be satisifed (https://github.com/glock45/swifter.git)

With a Package.swift of:

import PackageDescription

let package = Package(
  name: "MySwiftPackage",
  targets: [],
  dependencies: [
    .Package(url: "https://github.com/glock45/swifter.git", majorVersion: 1)
  ]
)

[harlanhaskins]

It's definitely the cause.

majorVersion: 1 means that it's going to look for a tag called 1.0.0, which this project doesn't have.

You'll need to use the .Package(url: String, _ version: Version) initializer.

The project does have a 1.0.2 tag.
.Package(url: "https://github.com/glock45/swifter.git", Version(1, 0, 2))

But that tag doesn't have Package.swift as it was created in October.

[cwagdev]

I believe majorVersion: 1 finds the newest 1.x.x version. I was just able to get swift build to pass by forking and creating a 1.0.3 tag on my fork.

import PackageDescription

let package = Package(
  name: "MySwiftPackage",
  targets: [],
  dependencies: [
    .Package(url: "https://github.com/cwagdev/swifter.git", majorVersion: 1)
  ]
)

[harlanhaskins]

Ooh, really? I thought it found the lowest version! That's great. Thanks!

[NSBrianWard]

Just curious if this is on the plan for resolution in the near future. Currently I'm on the fork, but I'd love to jump back in the main branch ASAP. Thanks!

[julien-c]

Planning on tagging a release later today, once I merge a main.swift example file for Linux.

[damian-kolakowski]

@harlanhaskins @cwagdev @NSBrianWard @julien-c
We got a new release 1.0.5.