<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><blockquote type="cite" class=""><div class="">On Apr 19, 2021, at 2:51 PM, Jason Liu <<a href="mailto:jasonliu@umich.edu" class="">jasonliu@umich.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div 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;" class="">On Mon, Apr 19, 2021 at 1:25 PM Craig Treleaven <<a href="mailto:ctreleaven@cogeco.ca" target="_blank" class="">ctreleaven@cogeco.ca</a>> wrote:</div><blockquote class="gmail_quote" 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; margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div class="">Also, why should we consider that MacPorts is in competition with Homebrew? Both MacPorts and Homebrew seem to have a sufficient number of contributors to keep going for the foreseeable future. Nether packaging system has to "win" nor does the other have to "lose". The projects do have differing philosophies that may make one more suitable than the other for particular users.</div></blockquote><div 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;" class=""><br class=""></div><div 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;" class="">Although this is a nice sentiment, I believe the reality is that MacPorts is in fact in competition with Homebrew. And not just Homebrew, but with other package managers as well, such as Munki, and even to some extent other deployment products such as Jamf/Casper and Jenkins. My belief is that the total number of systems running macOS as its operating system is the entire "pie" of systems that could potentially use one of these macOS package managers. In addition, the vast majority of users will only use one package management product, hence my opinion of why it's a pie with a limited number of potential users that gets divided up. The possible exception to only using one product per machine might be, say, in an enterprise setting (you can read my personal anecdote below for an example).</div><div 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;" class=""><br class=""></div><div 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;" class="">In addition, it has traditionally been the case that package management systems say on their websites that installing multiple package managers on one machine can cause problems... e.g. MacPorts doesn't work well with Fink and Homebrew, Homebrew doesn't work well with Fink and MacPorts, etc. People on this mailing list are tech savvy enough to deal with the potential conflicts that might occur regarding environment variables, $PATH order, etc. but the vast majority of users won't be, and thus would stick to using only one package manager. If one product "wins" by getting installed on a particular system, then the others "lose”.</div><br class="Apple-interchange-newline"></div></blockquote></div><div class=""><br class=""></div>I wasn’t trying to suggest that a user should install multiple package managers.<div class=""><br class=""></div><div class="">MacPorts needs contributors and maintainers to go forward. We don’t _need_ users! It is the same amount of work to create or update a package regardless of the number of users. Several of the packages I maintain have very few reported users…sometimes only me. <div class=""><br class=""></div><div class="">As long has we have a decent volume of people contributing to MacPorts the project will continue. As a port maintainer, it is gratifying to think that my work may be benefiting others. It is not that important whether it is 10 people or 10,000. I think that many of our maintainers do so because they need the ports that they are working on. IOW, they’d do so even if there were no other users. Obviously, several of our most prolific maintainers have different motivations.</div><div class=""><br class=""></div><div class="">To be cynical, I think Homebrew users are more commonly command line newbies and therefore probably generate a high volume of simple and repetitive questions. AKA ’support desk hell’! Perhaps we are fortunate that MacPorts users tend to be a little more savvy. ;)<br class=""><div class=""><br class=""></div></div><div class="">Craig</div></div><div class=""><br class=""></div></body></html>