Allow to symlink Package.swift to Tuist/Package.swift
#5562
Conversation
| } | ||
| try fileHandler.write(content, path: packageManifestPath, atomically: true) |
There was a problem hiding this comment.
Can we skip the process of writing another Package.swift?
There was a problem hiding this comment.
I don't think so, if we want SPM resolution and folders to be created in Tuist/Dependencies/SwiftPackageManager, then the Package should be located there.
It's more conveniente for those to be in a separate folder, so you can just gitignore the whole Tuist/Dependencies/SwiftPackageManager
There was a problem hiding this comment.
Does it need to be Tuist/Dependencies/SwiftPackageManager? We adopted that structure because we supported multiple package managers so I'm wondering if we should simplify things a bit and stick to SPM's convention.
There was a problem hiding this comment.
Having everything in Tuist/ would be strange I think. Anyway, it would be a breaking change and in case it would go in 4.0
danieleformichelli
changed the title
Package.swift to Tuist/Package.swiftPackage.swift to Tuist/Package.swift
|
Closing this, I'll rather add a config to specify the location of the Package.swift |
No description provided.