<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 dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Bjarne,<div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 5, 2021, at 4:16 PM, Bjarne D Mathiesen <<a href="mailto:macintosh@mathiesen.info" class="">macintosh@mathiesen.info</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">As I see it, we've got several problems/issues :<br class=""><br class="">2) how does one use macports in daily life ?<br class=""> we've got a section :<br class=""> <a href="https://trac.macports.org/wiki/howto" class="">https://trac.macports.org/wiki/howto</a><br class=""> that we collectively ought try to promote better & bring up-to-date<br class=""> & yes - I'm guilty here as the sections I've authored haven't been<br class=""> kept updated :-( In my defence, I didn't experience much ethusiasm /<br class=""> support for my efforts, so I more-or-less gave up.<br class=""> There was/is a lot of negative put downs :<br class=""> - "that's not recommended"<br class=""> - "we don't do it that way"<br class=""> instead of saying : "that's interesting !? why does he find it<br class=""> necessary doing it that way ?!? could we incorporate his ideas &<br class=""> improve upon them ?!?"<br class=""> and generally no feedback at all.<br class=""></div></div></blockquote><div><br class=""></div><div>We do have standards that aren’t always documented. Those hopefully get communicated with PR reviews. No one on the project is negative IMHO but I agree we aren’t always overly positive. If feedback is not followed then PRs tend to not get accepted. Please don’t take it personally. Also sometimes no one has gotten to it. Successful contributors who eventually become committers are the ones who are persistant self starters and follow our established standards. People who are knowledgable and contribute a lot of time and code can establish new standards. </div><div><br class=""></div><blockquote type="cite" class=""><div class=""><div class="">4) Public Relations<br class=""> As has been stated elsewhere, almost nobody knows about macports.<br class=""> Everybody references brew. I've just read a book on how to work with<br class=""> Terminal :<br class=""> <a href="https://www.apress.com/gp/book/9781484261705" class="">https://www.apress.com/gp/book/9781484261705</a><br class=""> and the go-to package manager is brew. Some of the stuff mentioned<br class=""> installed with brew isn't present in macports, but those are minor<br class=""> issues.<br class=""> A course of action ought to be, that when one of us sees brew<br class=""> referenced as !the! way to install something, then to take contact<br class=""> and get the site to reference macports too.<br class=""></div></div></blockquote><div><br class=""></div><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">Yes it’s safe to say that we don’t have anyone on the project who actively promotes it. We tend to simply fix and update ports and not be political or grandstanding about it. In the past, I have asked a few upstream projects to mention Macports as a method to install their project and given them instructions to use. </span></font></div><div class=""><br class=""></div></div><div class=""><br class=""></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">Cheers!</span></font></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">Frank</span></font></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class=""></span></font></div></div></body></html>