<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><font size="2" face="sans-serif" class="">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.</font><br class=""><br class=""><font size="2" face="sans-serif" class="">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.</font><br class=""><br class=""><font size="2" face="sans-serif" class="">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?<br class=""></font></div></blockquote></div><br class=""><div class="">High-ish. There are gaping holes in SwiftPM that are currently higher priority.</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">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.</div></body></html>