duplicates:

• SR-3951 Multi-Package Repository Support

Issue Description:

The evolution proposal for multi-package repos has been open for over a year. To us this is a vital feature and we're still wrestling with SwiftPM internals with every single swift release because of newly introduced SwiftPM bugs or "features" that break our admittedly somewhat hacky workflow of leaving all dependencies in an edited state.

The single-package git repo workflow does not fit our needs: it is actually much more of a hinderance than a help. For our case we need to be able to manage dependencies ourselves, but don't want to set up complex scripts to build various targets and submodules by hand. I am very frustrated that this, what to me seems to be the "base case", is so difficult in SwiftPM. I'm at the point of strongly considering forking SwiftPM and just deleting all the code paths that don't just "build".

Is there anything at all we can do to speed this proposal up? What if I made a PR for local non-git dependencies, for example?