<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="">The only solution offered by the developer of DetectX was to tell DetectX to ignore changes to macports plist files. <div class=""><br class=""></div><div class="">That seems to defeat the purpose of DetectX. </div><div class=""><br class=""></div><div class="">DetectX is supposed to warn you of possible nefarious changes to your system. Choosing to ignore a possible problem is no solution.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Nov 4, 2019, at 21:29, 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="">Well MacPorts isn't the program that's complaining, DetectX is. So I'd ask the developer of DetectX.</span></div></blockquote></div><br class=""></div></body></html>