[swift-build-dev] Hello SPM

[Daniel Dunbar]

Circling back on this...

> On Dec 7, 2015, at 10:23 AM, orta therox via swift-build-dev <swift-build-dev at swift.org> wrote:
> 
> 
>> On Dec 7, 2015, at 12:30 PM, Daniel Dunbar via swift-build-dev <swift-build-dev at swift.org <mailto:swift-build-dev at swift.org>> wrote:
>> 
>> Ok, great! Do you have existing infrastructure for analysis of those libraries? Would it be easy to write a tool to, e.g., count #s and types of libraries? Or create a summary of source layout styles?
> 
> I have a local machine with a download of every pod, from about 3 months ago. I can probably script this sort of thing, happy to take this one to direct mail if you have an idea of what you want.
> 
> Given that paths are, generally speaking, added in the Podspec, this can also be generated from the CocoaPods/Specs repo itself too. 

The high level question we would want to answer would be "how much work is it for people to conform to convention X". I could envision trying to automate that by taking the corpus of pods, applying some amount of automated transformations based on the known or proposed conventions and the Podspec, and then seeing if the project builds. If it wasn't too much work to build such a system then it could be invaluable in vetting convention proposals, but I'm not currently familiar enough with the ecosystem to know if this is viable or not.

If you think it is, that is totally something I would consider taking off list if/when I had some time to hack on it...

 - Daniel

> 
> _______________________________________________
> swift-build-dev mailing list
> swift-build-dev at swift.org
> https://lists.swift.org/mailman/listinfo/swift-build-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-build-dev/attachments/20151212/3a654445/attachment.html>