<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 25.06.2015, at 00:10, Christopher Ramos <<a href="mailto:chrisdavidramos@gmail.com" class="">chrisdavidramos@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Macports, like the Mac App Store, is *curated*; it's not the same thing as going to some fly-by-night website, downloading, and installing willy nilly.</span></div></blockquote></div><br class=""><div class="">But that’s the crucial thing which you don’t seem to understand, it’s exactly that.</div><div class="">Think of git as a downloader. </div><div class="">Git installs through MacPorts. Nothing bad will happen at this point.</div><div class="">You use git to clone a repository (in other words you are downloading a lot of text files). Nothing bad will happen at this point.</div><div class="">And that’s it. Whatever you are doing now with this repository is up to you. Git has done its part.</div><div class="">It’s almost exactly like going to any website with any browser and downloading *any* software. Once it’s downloaded it (the software) is sitting in your download folder and is doing nothing. The browser is done (it might have unpacked the archive the software came in, though).</div><div class="">You need to actively install or run that software to harm your system. Is that then the browser’s fault?</div><div class=""><br class=""></div><div class="">Back to MacPorts and Git.</div><div class="">So you cloned a repository with Git and nothing bad happens. and Git is done.</div><div class="">Now you will most likely want to do something with the code you cloned. At this time, you will use the autotools or cmake or xcode or whatever to build the program out of the code. Some ways may cause problems further down the line (“make install” for example) but that is certainly never the fault of the download tool. It may be the fault of some script or other compile tool OR the users fault for running “make install” without knowing what will happen next…</div><div class=""><br class=""></div><div class="">When MacPorts uses Git to clone a repository and will then build software from this repository, it IS MacPorts responsibility to make sure nothing bad happens, or rather when something bad happens try to prevent it. But again, the problem is not Git, the problem is elsewhere.</div><div class=""><br class=""></div><div class="">Dom</div></body></html>