<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=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 30.07.2020 um 08:03 schrieb Ken Cunningham <<a href="mailto:ken.cunningham.webuse@gmail.com" class="">ken.cunningham.webuse@gmail.com</a>>:</div><div class=""><pre class="" style="caret-color: rgb(0, 0, 0); font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; white-space: pre-wrap; background-color: rgb(255, 255, 255);">I only raise the idea as people are already doing this, and submitting such ports, and before we have too many, there is an opportunity to say how it should best be done (custom category, naming convention, etc).</pre></div></blockquote></div>Reminds me of an earlier conversation at <a href="https://github.com/macports/macports-ports/pull/6767#discussion_r402584006" class="">https://github.com/macports/macports-ports/pull/6767#discussion_r402584006</a> <div class=""><br class=""></div><div class="">I do see some benefits is formalizing binary-only ports and to adapt the build and distribution scheme for it. Could save resources and development time and make those ports easily recognizable for those who care about the different way it was built.<br class=""><div class=""><br class=""></div><div class=""><br class=""></div></div></body></html>