<font size=2 face="sans-serif">Thanks Max for your response! I see what
you are saying about your proposal having an impact on the feature we are
thinking of. It would probably work best if we can align our feature with
the changes you plan to include in your proposal. Do you think you will
be documenting/adding your proposal to the list sometime this week or the
following?<br><br>Regards,<br> Ricardo Olivieri<br> Software Engineer</font><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Max Howell <max.howell@apple.com></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Ricardo N Olivieri/Austin/IBM@IBMUS</font><br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">swift-build-dev@swift.org</font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">02/17/2016 01:30 PM</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [swift-build-dev]
Swift Package Manager - Support for downloading/installing external dependencies
that a Swift Package may have</font><br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">max.howell@apple.com</font><br><hr noshade><br><br><br><font size=3>Hi Ricardo,</font><br><br><font size=3>Respectfully I’d rather you waited, I have a proposal
in the works for major changes to the content of Package.swift and this
would have quite an impact on this feature.</font><br><br><font size=3>I will try to get the proposal to the list soon.</font><br><br><font size=3>If you want to do the PR anyway we will accept it provided
it is not executed as a default (requiring a flag marked explicitly as
temporary) and that we will remove the flag when the feature is properly
implemented and integrated.</font><br><br><font size=2 face="sans-serif">Hello Max, just following up on the
previous email. Does the approach described in the previous message fit
with the plans and vision for SPM? If it does and our team were to take
a first shot at implementing something like it, would our pull request
have good chances of getting merged with the SPM repo?<br><br>Regards,<br> Ricardo Olivieri<br> Software Engineer</font><font size=3><br><br></font><font size=1 color=#5f5f5f face="sans-serif"><br>From: </font><font size=1 face="sans-serif">Ricardo
N Olivieri/Austin/IBM</font><font size=1 color=#5f5f5f face="sans-serif"><br>To: </font><font size=1 face="sans-serif">Max
Howell <</font><a href=mailto:max.howell@apple.com><font size=1 color=blue face="sans-serif"><u>max.howell@apple.com</u></font></a><font size=1 face="sans-serif">></font><font size=1 color=#5f5f5f face="sans-serif"><br>Cc: </font><a href="mailto:swift-build-dev@swift.org"><font size=1 color=blue face="sans-serif"><u>swift-build-dev@swift.org</u></font></a><font size=1 color=#5f5f5f face="sans-serif"><br>Date: </font><font size=1 face="sans-serif">02/01/2016
09:12 PM</font><font size=1 color=#5f5f5f face="sans-serif"><br>Subject: </font><font size=1 face="sans-serif">Re:
[swift-build-dev] Swift Package Manager - Support for downloading/installing
external dependencies that a Swift Package may have</font><font size=3><br></font><hr noshade><font size=3><br></font><font size=2 face="sans-serif"><br>Thanks Max again for your response.</font><font size=3><br></font><font size=2 face="sans-serif"><br>I see what you are saying about having SPM fail the build and output suggested
commands to install the missing system-packages (as opposed to having SPM
perform system-package installations).</font><font size=3><br></font><font size=2 face="sans-serif"><br>We are still wondering if we could have a solution built into SPM that
would not required any manual intervention from a human. For instance,
would implementing something like the following be in the plans for SPM
(this is somewhat similar to the original option #1 we shared previously)?</font><ul><li><font size=2 face="sans-serif">Swift Packages can specify dependencies
on other libraries that are not Swift Packages (such as C libraries). The
Swift Package Manager could then "parse" this metadata, download
the C code for that external dependency (say, from the its GitHub repo),
compile it, and make it available to other Swift Packages through the module.modulemap
file. The metadata could be part of the Packages.swift file or a new file
for specifying dependencies that are not Swift Packages.</font></ul><font size=2 face="sans-serif"><br>Your thoughts?</font><font size=3><br></font><font size=2 face="sans-serif"><br>Regards,<br> Ricardo Olivieri<br> Software Engineer</font><font size=3><br><br><br><br></font><font size=1 color=#5f5f5f face="sans-serif"><br>From: </font><font size=1 face="sans-serif">Max
Howell <</font><a href=mailto:max.howell@apple.com><font size=1 color=blue face="sans-serif"><u>max.howell@apple.com</u></font></a><font size=1 face="sans-serif">></font><font size=1 color=#5f5f5f face="sans-serif"><br>To: </font><font size=1 face="sans-serif">Ricardo
N Olivieri/Austin/IBM@IBMUS</font><font size=1 color=#5f5f5f face="sans-serif"><br>Cc: </font><a href="mailto:swift-build-dev@swift.org"><font size=1 color=blue face="sans-serif"><u>swift-build-dev@swift.org</u></font></a><font size=1 face="sans-serif">,
Samuel Kallner <</font><a href=mailto:KALLNER@il.ibm.com><font size=1 color=blue face="sans-serif"><u>KALLNER@il.ibm.com</u></font></a><font size=1 face="sans-serif">>,
Daniel Firsht/Austin/IBM@IBMUS, Andrew M Trice/Washington/IBM@IBMUS, Robert
F Dickerson/Austin/IBM@IBMUS</font><font size=1 color=#5f5f5f face="sans-serif"><br>Date: </font><font size=1 face="sans-serif">01/28/2016
01:08 PM</font><font size=1 color=#5f5f5f face="sans-serif"><br>Subject: </font><font size=1 face="sans-serif">Re:
[swift-build-dev] Swift Package Manager - Support for downloading/installing
external dependencies that a Swift Package may have</font><font size=1 color=#5f5f5f face="sans-serif"><br>Sent by: </font><a href=mailto:max.howell@apple.com><font size=1 color=blue face="sans-serif"><u>max.howell@apple.com</u></font></a><font size=3><br></font><hr noshade><font size=3><br><br></font><font size=2 face="sans-serif"><br>Thanks Max for your answer. To your point, thinking about it more, it's
probably not a great idea to have SPM execute arbitrary scripts.<br><br>It is good news to hear that something similar to option #1 could be implemented
and that there are plans to provide something as part of SPM that can take
of installing/downloading external [non-Swift package] dependencies that
a Swift Package may depend on.<br><br>Does providing this functionality in SPM have a high priority? Any other
details about the plans for this feature that could be shared at this point?</font><font size=3><br><br>High-ish. There are gaping holes in SwiftPM that are currently higher priority.<br><br>This ticket should wait for my up-coming proposal that will improve module-map-packages
IMO. Then we can put this in there and implement it at the same time.<br><br>IMO it should work like Homebrew’s caveats. If the build fails it outputs
suggested commands to install the missing system-packages, then the user
can type those commands in if they so choose.<br><br><br></font><br><br><br><BR>