<div dir="ltr"><div><div>Thank you very much for the informative update. I hadn't seen the news until just now after reading your messag. It looks like this has to do with the great news about MaxCDN announced on March 13th 2016. No wonder everything seemed faster (it was a bit disorienting to a MacPorts long timer like me). Its great to see MacPorts is thriving. That said, we must be ever more vigilant about our Macs and iOS machines, including MacPorts security, given the nefarious world we live in (including, regrettably, the so-called "friendly fire"). <br><br></div>Thanks,<br><br></div>-T<br><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 24, 2016 at 5:34 AM, Brandon Allbery <span dir="ltr"><<a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><span class=""><div class="gmail_quote">On Thu, Mar 24, 2016 at 11:26 AM, Tabitha McNerney <span dir="ltr"><<a href="mailto:tabithamc@gmail.com" target="_blank">tabithamc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div>I have a Mac running OS X Yosemite 10.10.5. I made and installed MacPorts 2.3.3 from source on this machine (with Xcode 7.2.1). All seems well (I've been using MacPorts for many years). <br><br>After sudo port selfupdate runs successfully, when I attempt to install a new port with the proverbial "port install xyz" where xyz is the name of the port, the port installs fine but the port's distfile does not show up in the expected location. Take ncurses for example, for my standard configuration (where the prefix is /opt/local) I should see both:</div></blockquote></div><br></span>MacPorts has had the ability to install prebuilt packages when a port has a compatible license and is requested with default variants for many years. It's only relatively recently that we've had the ability to *build* those packages, though (buildbot infrastructure and storage). If you watch the install closely, you'll see it trying to download a prebuilt package before downloading distfiles and building locally.<br><div><br></div><div>If you need to have things only built locally, you can use the -s option or modify the "buildfromsource" option in /opt/local/etc/macports/macports.conf. (If you've been using a MacPorts installation on that machine for a long time, you may want to review that file against /opt/local/etc/macports/macports.conf.default to see what options have been added and maybe change their defaults if needed.)</div><span class="HOEnZb"><font color="#888888"><div><br>-- </div><div><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</font></span></div></div>
</blockquote></div><br></div></div>