<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=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 6, 2020, at 12:16 PM, Craig Treleaven <<a href="mailto:ctreleaven@macports.org" class="">ctreleaven@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; 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;"><br class=""></div></div></blockquote><br class=""><blockquote type="cite" class=""><div class=""><div class="" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; 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;">Personally, I don’t see any compelling reason why the MacPorts project should want to go in this direction. The first paragraph on our homepage says:</div></div></blockquote><br class=""></div><div>Actually, I’m perfectly happy with a blanket “NO” on all this, if that is the outcome.</div><div><br class=""></div><div>What I am trying to avoid is a bunch of these slipping in with no organization to it at all, for all these reasons.</div><div><br class=""></div><div>And IF it is done, please make it SIMPLE.</div><div><br class=""></div><div>no cryptic commands that 1 person in 10,000 can remember. MacPorts is already too full of that kind of thing.</div><div><br class=""></div><div>K</div><br class=""></body></html>