<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 10, 2015, at 1:43 AM, Ugo Arangino &lt;<a href="mailto:swift@ua94.de" class="">swift@ua94.de</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote type="cite" class="">On 05.12.2015, at 16:13, Joe Groff &lt;<a href="mailto:jgroff@apple.com" class="">jgroff@apple.com</a>&gt; wrote:<br class=""><br class=""><blockquote type="cite" class="" style="font-family: SourceCodePro-Regular;"><br class="">On Dec 4, 2015, at 8:49 PM, Daniel Dunbar &lt;<a href="mailto:daniel_dunbar@apple.com" class="">daniel_dunbar@apple.com</a>&gt; wrote:<br class=""><br class=""><br class=""><blockquote type="cite" class="">On Dec 4, 2015, at 6:37 PM, Ugo Arangino &lt;<a href="mailto:swift@ua94.de" class="">swift@ua94.de</a>&gt; wrote:<br class=""><br class="">Why is the Dynamic linker DT_RPATH set, instead of configure it like this `/etc/ld.so.conf.d/swift.conf` or&nbsp;copying the libraries to a appropriate place?<br class=""></blockquote><br class="">For the initial release, we felt it was more important for things to work locally (and simply) for people&nbsp;downloading our snapshots than to support this and have more complicated installation instructions.&nbsp;<br class=""></blockquote></blockquote><div class=""><br class=""></div><div class="">Will this be a solution to install Swift easy and on an appropriate directory?</div>&nbsp;$ wget -O - <a href="https://swift.org/install-ubuntu14.04.sh" class="">https://swift.org/install-ubuntu14.04.sh</a> | bash<br class=""></div></div></blockquote><div><br class=""></div><div>There was a pull request to this effect; you might weigh in on the issue there. Some people have security concerns about piping to sh, for better or worse.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote type="cite" class=""><blockquote type="cite" class="" style="font-family: SourceCodePro-Regular;">We also suspected that people would quickly try things like building Docker images with Swift, and this problem&nbsp;doesn't show up for users who are building their projects that way.<br class=""></blockquote></blockquote><div class=""><br class=""></div>An other&nbsp;solution would be, to offer `.deb` packages for `libswiftCore.so` ...<div class="">So other packages can have `libswiftCore.so` ... as&nbsp;package dependency.</div><div class="">In addition to this the Swift compiler can be offered as `.deb` package, too.</div><div class=""><br class=""></div><div class="">On OS X it is also enough to run the `swift-[...]-osx.pkg` installer.<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class="" style="font-family: SourceCodePro-Regular;">That said, we would welcome concrete proposals for how to improve the support for portable or distributable&nbsp;binaries. Those proposals should take into account whatever is happening with regard to system Swift packages.<br class=""></blockquote></blockquote><div class=""><br class=""></div><br class=""><blockquote type="cite" class="">In a previous thread, someone asked about statically linking in libswiftCore. That seems like a reasonable&nbsp;configuration to support on Linux to get easily-deployable independent binaries.<br class=""></blockquote><br class="">I have read the thread: "building static binaries / reducing library dependencies?" &lt;<a href="https://lists.swift.org/pipermail/swift-users/2015-December/000008.html" class="">https://lists.swift.org/pipermail/swift-users/2015-December/000008.html</a>&gt;<div class=""><br class=""></div><div class="">I don’t know if static linking can lead to&nbsp;license problems.&nbsp;</div><div class="">For example, if I want to publish something with the GPL License.</div></div></div></div></blockquote><div><br class=""></div><div>Swift is licensed under Apache with the runtime exception, which should be GPL compatible.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">P.S.&nbsp;I apologize for my English. I am a German student.</div></div></div></blockquote><br class=""></div><div>No worries, your English is fine!</div><div><br class=""></div><div>-Joe</div><br class=""></body></html>