<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 class="">A standard install command grabs pre-built stuff from <a href="https://packages.macports.org/privoxy-pki-bundle" class="">https://packages.macports.org/privoxy-pki-bundle</a>. This pre-built stuff is inevitably stale because it inevitably contains expired certs. We want to port to install stuff, just not pre-built expired stuff.</div><div class=""><br class=""></div><div class="">The desired behavior is to always install from “source,” i.e. the behavior that goes with “port -s install” which always installs the latest up-to-date PKI. </div><div class=""><br class=""></div><div class="">How does one write a Portfile to prevent installs from being cached at <a href="https://packages.macports.org/privoxy-pki-bundle" class="">https://packages.macports.org/privoxy-pki-bundle</a> ? </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div style="margin: 0px; font-stretch: normal; font-size: 24px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">sudo port install privoxy-pki-bundle</span></div><div style="margin: 0px; font-stretch: normal; font-size: 24px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">---> Computing dependencies for privoxy-pki-bundle</span></div><div style="margin: 0px; font-stretch: normal; font-size: 24px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">---> Fetching archive for privoxy-pki-bundle</span></div><div style="margin: 0px; font-stretch: normal; font-size: 24px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">---> Attempting to fetch privoxy-pki-bundle-3.0.33_3+user_pki_bundle.darwin_21.x86_64.tbz2 from <a href="https://packages.macports.org/privoxy-pki-bundle" class="">https://packages.macports.org/privoxy-pki-bundle</a></span></div></blockquote></div><div class=""><div style="margin: 0px; font-stretch: normal; font-size: 24px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div></div><div><br class=""><blockquote type="cite" class=""><div class="">On May 22, 2022, at 5:19 AM, Ryan Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On May 21, 2022, at 12:40, Steven Smith wrote:<br class=""><br class=""><blockquote type="cite" class="">Is there a way to achieve the second objective: prevent MacPorts from building and caching its own copy of the port contents, which for this port will inevitably be filled with expired certificates?<br class=""><br class="">Right now, avoiding this issue requires installing the port from “source” with `port -s install`.<br class=""></blockquote><br class="">Again I don't understand the question.<br class=""><br class="">If you don't want the port to install anything, write the destroot phase to do that. Except that a port must install at least one file. But this doesn't sound like what you're asking.<br class=""><br class="">Why will what the port installs inevitably be filled with expired certificates? What would be the cause of that happening?<br class=""><br class="">If the port's contents should be changed (in the binaries produced by the buildbot and on user systems) then change the port to install the new contents and increase its revision.<br class=""><br class="">Perhaps there is something unique about this software that I don't understand. (I have no idea what this software is.)<br class=""><br class=""></div></div></blockquote></div><br class=""></body></html>