<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 20 Feb 2022, at 19:01, Joshua Root <<a href="mailto:jmr@macports.org" class="">jmr@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Gerben Wierda wrote:<br class=""><br class=""><blockquote type="cite" class="">So, how would you go about finding the ports on which what is actually installed depends?<br class=""><br class="">E.g.: if I have dovecot+solr8 installed, how would I find out which ports dovecot truly depends on on my system?<br class=""></blockquote><br class="">Is there a reason that information is required apart from curiosity? MacPorts won't install anything you didn't ask for unless it's a dependency of something you did ask for, and if you try to uninstall something that is still needed by something else, it will complain.<br class=""></div></div></blockquote><div><br class=""></div><div>I’e been hit with MacPorts hosing my setup when cleaning a while back so I’ve become pretty fearful/careful. It’s in the archives of this mailing list.</div><div><br class=""></div><div>So, when I want to clear/uninstall something, I want to check if I do not break something and MacPorts turned out to be not perfectly safe on that front.</div><div><br class=""></div><div><div class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><div class="">Gerben Wierda (<a href="https://www.linkedin.com/in/gerbenwierda" class="">LinkedIn</a>)</div><div class=""><a href="https://ea.rna.nl/" class="">R&A IT Strategy</a> (main site)<br class="">Book: <a href="https://ea.rna.nl/the-book/" class="">Chess and the Art of Enterprise Architecture</a><br class="">Book: <a href="https://ea.rna.nl/the-book-edition-iii/" class="">Mastering ArchiMate</a><br class=""></div></div></div></div></div></div></div></div></div></div><div><br class=""><blockquote type="cite" class=""></blockquote></div></div><blockquote type="cite" class=""><div class=""><div class=""><br class="">'port deps dovecot and installed' will usually work, though it uses the current Portfile, so if the port is outdated the dependencies could have changed. Use rdeps instead of deps if you want all recursive dependencies, and use the --no-build option with either action to exclude dependencies only needed at build time.<br class=""><br class="">- Josh<br class=""><br class=""></div></div></blockquote></div><br class=""></body></html>