Evolving SwiftPM Builds with Swift Build

[taylorswift]

@jakepetroules

That said, to clarify what I think you were trying to emphasize to our community partners, our current focus on getting SwiftPM re-platformed on top of Swift Build means it may be best to largely hold off on proposals related to new manifest API until that transition is complete, so that we don't spend effort trying to implement that functionality in two different build system engines at once.

i’m curious to know how this will impact [Pitch] Replaceable Library Plugins , which does not introduce any new API to the manifest, but does add some minor extensions to the ArtifactsArchiveMetadata JSON format, and changes nine files within the SwiftPM source code.

RLPs are very mission-critical to a number of key stakeholders in the community, especially the server-side Swift community, and some members of the community have invested significant resources into advancing this feature. i think it could become more challenging to justify additional external investment in Swift in the future if existing investments, like [Pitch] Replaceable Library Plugins , were swept aside or allowed to become stale because of conflicting timelines between organizations. i think it is important for both Apple and community contributors to coordinate the upstreaming of these features to avoid wasted effort.