<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Some of those will have been required to build other ports (such as automake or bison). If you don't use them directly, you may not need them...until you update or install a port that needs them to build, in which case reinstalling them would happen automatically, but slow that down.<div class=""><br class=""></div><div class="">It'd probably be a good idea to do the setrequested bit at least for all those you know you want, even if there are plenty you don't know one way or the other.<br class=""><div><br class=""></div><div>For the ones you don't think you want, you could always deactivate them, run a port rev-upgrade, and see if anything breaks. If not, you can probably remove them (although again, they may well get reinstalled at some future update). I think that'd be reasonably safe, although probably unnecessary - assuming ports properly identify what the depend on (they may not all be perfect), you should get a warning if you try to uninstall something that's currently needed.</div><div><br class=""></div><div>If you just want to free up some space (but not necessarily all possible space), how about</div><div>sudo port uninstall inactive and unrequested</div><div><br class=""></div><div>That would just get rid of older versions of those. You could also just remove all the inactive ports, but occasionally one wants to revert something if there's a problem.</div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On May 3, 2020, at 17:43, Michael Newman via macports-users <<a href="mailto:macports-users@lists.macports.org" class="">macports-users@lists.macports.org</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; line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class="">On May 3, 2020, at 21:28, Ryan Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Courier; font-size: 24px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Look at the output of "port installed unrequested". If you see any port in that list that you actually do want, indicate that by running "sudo port setrequested thePortName".</span></div></blockquote><br class=""></div><div class="">This is easier said than done.</div><div class=""><br class=""></div><div class="">The output of port installed unrequested has 461 items; most of which I don't recognize. Lynx is there and I know I want that. But the first port listed is a52dec. I don't know what that is, or what it does or whether or not I want it. I also see atk, automake, bison, harfbuzz, and many others which mean nothing to me.</div><div class=""><br class=""></div><div class="">Sure, I can do some research to figure out what each of these does, but then I will still have no idea whether or not I want them. Did I request some in the distant past? Am I still using them? No idea.</div><div class=""><br class=""></div><div class="">It seems to be a very daunting task. </div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""></div></div></blockquote></div><br class=""></div></body></html>