I just want to add that I have been immensely frustrated and inconvenienced by the lack of this, what I believe is, basic and essential feature in the SwiftPM.
On Fri, Jul 21, 2017 at 9:32 AM, Ankit Aggarwal via swift-users < swift-users@swift.org> wrote: > I’m just surprised the idea of a "local dependency" is not seen as a first > class citizen in SwiftPM, still trying to understand the logic behind that. > Maybe you can give me an idea of the reasoning behind this? > > > I understand your usecase will benefit a lot from the local dependency > feature. We did consider adding this feature, I think the main concern was > package authors ending up publishing package which only works for them > incase they forget updating their manifest before a release. Also, note > that SwiftPM is still under heavy development and we can definitely > re-consider adding this! > > Also, I think this is a good usecase of a multipackage repository feature. > We don't have that yet but you can read some of the discussion here > <https://lists.swift.org/pipermail/swift-build-dev/Week-of-Mon-20161107/000722.html> > . > > PS: We also have a slack channel if you want to hang out - > https://lists.swift.org/pipermail/swift-build-dev/ > Week-of-Mon-20160530/000497.html > > _______________________________________________ > swift-users mailing list > swift-users@swift.org > https://lists.swift.org/mailman/listinfo/swift-users > >
_______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
