<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Apr 3, 2021, at 8:21 PM, <a href="mailto:Wowfunhappy@gmail.com" class="">Wowfunhappy@gmail.com</a> <<a href="mailto:wowfunhappy@gmail.com" class="">wowfunhappy@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" 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=""><div class="">On 2021-1-27 02:57 , Andrew Janke wrote:</div><div class="">I didn't know that! I must be behind the times with the state of MacPorts. Thanks for the update.</div></blockquote></blockquote><blockquote type="cite" class=""><div class="">About a decade behind -- the buildbot went live in 2011. ;)</div><div class="">- Josh</div></blockquote><br class=""><div class="">I see this misconception <i class="">all over the place</i>, that Homebrew is fast because it uses prebuilt binaries, whereas MacPorts makes you wait while software is compiled. It can't <i class="">just</i> be due to outdated information, if we're more than a decade out from when the buildbot went live.</div><div class=""><br class=""></div><div class="">I know it's just one data point, but I thought the replies I got on this Hacker News comment today were interesting. I can understand why he/she got confused, and I wonder if there's anything MacPorts could do to make it clearer. <a href="https://news.ycombinator.com/item?id=26678498" class="">https://news.ycombinator.com/item?id=26678498</a></div></div></div></blockquote></div><br class=""><div class="">It happens that I just did a self update and upgraded 20 ports on 10.15. 6 or the 20 were built from source. I believe this is higher than usual due to the backlog on the 10.15 builbot. Even in the best case, however, a fair number of ports will be built from source for the well-known reasons. It would be interesting to know, say, how many of our most-requested ports are always built from source.</div><div class=""><br class=""></div><div class=""><a href="https://ports.macports.org/statistics/ports/?days=30&first=-req_count&second=-total_count&third=port" class="">https://ports.macports.org/statistics/ports/?days=30&first=-req_count&second=-total_count&third=port</a></div><div class=""><br class=""></div><div class="">Eg, git is our second-most requested port and it is always built from source AFAIK.</div><div class=""><br class=""></div><div class="">Almost any reasonably complex package will have some of its dependencies that must be built from source. </div><div class=""><br class=""></div><div class="">To the average user, I would suggest that we should emphasize that MacPorts installs binaries whenever allowed by licensing but makes a serious effort to avoid contravening the various open source licenses. Plus MacPorts offers many more options (“variants”) to customize installations and offers a wide breadth of packages.</div><div class=""><br class=""></div><div class="">Craig</div><div class=""><br class=""></div></body></html>