This is indeed something we have discussed and agree it would make sense to add, just haven't gotten there yet.
Patches in this direction are welcome, although I recommend as with any new feature coming up with a concrete proposal and outline before you set in on the implementation...
On the Swift package manager page on swift.org <http://swift.org/> (https://swift.org/package-manager/#example-usage) the requirements for creating a package/application are clearly outlined, but why not include a command in the swift tool for autogenerating the require? I did a quick look and didn’t see any existing discussion, so I apologize if this has already been discussed.
Example of the tool command: `swift init foo --type=(lib|app)`
One question we would need to resolve is whether or not the tool should be interactive. If one goal
Would create a new directory called “foo” with the following tree structure for a project of type app:
This is most likely not the initial layout we want to recommend, because it is less obvious how to migrate upwards. This flat layout is a little confusing as well to newcomers because Package.swift here *isn't* part of their actual larget. We included support for this style for "micro-framework" type packages, where it can be useful for the simplicity of the project to be obvious in the initial repo view, but this is something more advanced users can come to discover.
And for project of type lib:
In both cases Package.swift would contain something basic like:
let package = Package(
I'd probably leave dependencies: out of this. I presume you added it to help people know where to add things, but another related thing we would like to see develop is tools for automatically editing this file (e.g., a command to add a new dependency). Tools like that will help people get their manifest files right w/o needing to memorize the package syntax.
On Dec 5, 2015, at 1:01 PM, Lander Brandt via swift-build-dev <email@example.com> wrote:
swift-build-dev mailing list