<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>But that’s not what HE said. He disagreed with you.<br></div><div><br></div><div>For myself, I don’t need reasons not to use Homebrew. I’d need reasons TO use Homebrew.<br></div><div><br></div><div>MacPorts does what I want in the way that I want it. What else does it need to do?</div><div><br></div><div id="sig39065985"><div class="signature">-- <br></div><div class="signature">Marc Wilson<br></div><div class="signature"><a href="mailto:posguy99@gmail.com">posguy99@gmail.com</a><br></div></div><div><br></div><div><br></div><div>On Sat, Jun 11, 2022, at 1:53 PM, Michele Venturi wrote:<br></div><blockquote type="cite" id="qt" style=""><div dir="auto"><div>That's what I said, no coherence or coordination.<br></div><div dir="auto">So what are your reasons to not use HomeBrew?<br></div></div><div><br></div><div class="qt-gmail_quote"><div dir="ltr" class="qt-gmail_attr">On Sat, Jun 11, 2022, 22:40 Jim DeLaHunt <<a href="mailto:list%2Bmacports-dev@jdlh.com">list+macports-dev@jdlh.com</a>> wrote:<br></div><blockquote class="qt-gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;"><div>Hello, Jordan:<br></div><div> <br></div><div> Welcome (back to) MacPorts!<br></div><div> <br></div><div> I am nobody official with the project. I just try to make contributions <br></div><div> to a few ports and documentation pages where I can. But in this project, <br></div><div> lots of people contribute, each in their own way.<br></div><div> <br></div><div> On 2022-06-11 07:07, Jordan via macports-dev wrote:<br></div><div> > Hi friends,<br></div><div> > <br></div><div> > <br></div><div> > First of all thank you for your work! I use MacPorts exclusively for a <br></div><div> > few different reasons and am looking to contribute to the project....<br></div><div> <br></div><div> I for one would be glad to have your contributions.<br></div><div> <br></div><div> > There is one aspect of MacPorts that has me a little down in the dumps <br></div><div> > and that's is its _apparent_ (but likely not true) neglected state. I <br></div><div> > think it's perhaps under maintained currently due to a lack of <br></div><div> > people-power? I say so because I'd love to see more people using <br></div><div> > MacPorts so I wonder if there's any "modernisation" (for lack of a <br></div><div> > better word) to be had here? ... so perhaps some usage compared to <br></div><div> > things like Homebrew can be gained back since I'd love to see this <br></div><div> > project used more.<br></div><div> <br></div><div> I think it is not fair to say MacPorts overall is in a neglected state. <br></div><div> Its core purpose is to help people compile a wide range of freely <br></div><div> available software on the macOS platform. As part of that it helps <br></div><div> gather the related software needed to make the requested software work. <br></div><div> I think that this aspect of MacPorts works very well. It gets a lot of <br></div><div> care and attention. There is a lot of activity. For instance, I just <br></div><div> moved onto an M1 Mac, and I see a lot of support for compiling software <br></div><div> with the M1 CPU's architecture. That is the opposite of neglect.<br></div><div> <br></div><div> Now, certain aspects of the project are neglected. You mention the <br></div><div> timeline on Trac. That's a page of documentation.<br></div><div> <br></div><div> When you say "modernisation", I think you mean, changes to how MacPorts <br></div><div> work to make it easier or better for some audience. I think that is best <br></div><div> approached as a collection of small projects, each with a specific <br></div><div> understanding of a problem, and its own goal for an improvement. One way <br></div><div> to proceed is to start a macPorts-dev thread for each of these ideas <br></div><div> (and each with a different Subject: line, please).<br></div><div> <br></div><div> You mention believing that `sudo` probably scares new users. Maybe so, <br></div><div> maybe not. A first step is to gather some evidence whether this is true. <br></div><div> A next step is to figure out why the port tool requires use of `sudo`. A <br></div><div> third step is to figure out what alternative way the port tool could <br></div><div> work which does not require `sudo`. For my part, use of `sudo` is no <br></div><div> problem at all. MacPorts is a command-line tool for system maintenance. <br></div><div> I am used to system maintenance tools requiring administrator passwords. <br></div><div> `sudo` is a command-line way of requiring a password.<br></div><div> <br></div><div> I will also say that competing with Homebrew about which project has <br></div><div> more users is not very interesting to me. Homebrew works well for some <br></div><div> people. MacPorts works well for some people. I'm interested in helping <br></div><div> MacPorts be the best MacPorts it can be. If Homebrew ends up with more <br></div><div> users, that is no big deal to me.<br></div><div> <br></div><div> > Also, as a tacked-on issue I am working on...<br></div><div> <br></div><div> I suggest you start a separate email thread for each issue. If you try <br></div><div> to discuss deleting files on uninstall as part of a thread with the <br></div><div> Subject: of "MacPorts status", which was originally about your offer to <br></div><div> help, I suspect you will lose a lot of readers.<br></div><div> <br></div><div> Anyhow, I look forward to seeing you in the email list, and in the trac <br></div><div> tickets, and in the Pull Requests! Glad to have your help.<br></div><div> <br></div><div> Best regards,<br></div><div> —-Jim "just another MacPorts user/contributor" DeLaHunt<br></div><div> <br></div></blockquote></div></blockquote><div><br></div></body></html>