<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></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 <<a href="mailto:swift@ua94.de" class="">swift@ua94.de</a>> 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 <<a href="mailto:jgroff@apple.com" class="">jgroff@apple.com</a>> 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 <<a href="mailto:daniel_dunbar@apple.com" class="">daniel_dunbar@apple.com</a>> wrote:<br class=""><br class=""><br class=""><blockquote type="cite" class="">On Dec 4, 2015, at 6:37 PM, Ugo Arangino <<a href="mailto:swift@ua94.de" class="">swift@ua94.de</a>> 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 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 downloading our snapshots than to support this and have more complicated installation instructions. <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> $ wget -O - <a href="https://swift.org/install-ubuntu14.04.sh" class="">https://swift.org/install-ubuntu14.04.sh</a> | bash<br class=""><br 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 doesn't show up for users who are building their projects that way.<br class=""></blockquote></blockquote><div class=""><br class=""></div>An other solution would be, to offer `.deb` packages for `libswiftCore.so` ...<div class="">So other packages can have `libswiftCore.so` ... as 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=""></div></div></div></blockquote></div><br class=""><div class="">Ready-to-install packages would be awesome, though it would require someone to implement and maintain that package, and there's still configuration complexity for users who need to install that package, and potentially maintain different versions as Swift's ABI converges. Static linking would avoid all that. The ease of deployment of static libraries seems to be one of the killer features that leads people to suffer programming in Go.</div><div class=""><br class=""></div><div class="">-Joe</div></body></html>