<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="">MacPorts is by nature not just one thing. There's the "port" command, related commands, the structure of Portfiles; there's the servers that deliver up both pre-built executables AND whether for lack of capacity to pre-build or because certain ports need to be locally built, may also deliver packaged source that builds locally. All of that and maybe more is MacPorts itself.<div class=""><br class=""></div><div class="">And then there's the individual ports. Those are maintained (or sometimes not) by different people, and very dependent on the "upstream" supplier of the project, who may not always accept patches specific to make it work on a Mac (let alone older macOS versions), so that port may have to have and apply its own patches, which adds delay between upstream update and port update.</div><div class=""><br class=""></div><div class="">Even IF there was one vision of what MacPorts should do, that's quite a lot and although it really tries, CANNOT guarantee consistent results on everything for everyone - nothing can, and esp. nothing with mostly unpaid volunteers can (although I think Apple provides the servers).<br class=""><div><br class=""></div><div>Taking all that into account (and I'm NOT part of the "team" just another user, so some of that may not be 100% accurate), you might consider clarifying just what you want.</div><div><br class=""></div><div>Doubtless brew and fink also have some difficulties getting everything just right (modulo different opinions of what "just right" might be). So you might find that you'll NEVER be happy. If that turns out to be the case, it might be your expectations rather than anyone else's performance needs to be re-evaluated.</div><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 27, 2022, at 09:25, Michele Venturi <<a href="mailto:dardo82@gmail.com" class="">dardo82@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" class="">That's what I said and anyway I repeat for the nth time<div dir="auto" class="">to people that doesn't want to know it: it's YOUR stuff,</div><div dir="auto" class="">YOU should know what it is, I'm not here to tell you what</div><div dir="auto" class="">to do you with it, this just a friendly reminder to decide...</div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il dom 27 mar 2022, 01:42 Ryan Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>> ha scritto:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mar 26, 2022, at 00:48, Michele Venturi wrote:<br class="">
<br class="">
> As usual this project too is a mess because everyone has a different idea of what it is,has been and will be.<br class="">
<br class="">
If you have constructive criticism for changes that should be made, feel free to start discussions about them. Otherwise you may be happier using something else.<br class="">
<br class="">
</blockquote></div>
</div></blockquote></div><br class=""><div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); 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; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div>-- <br class="">eMail:<span class="Apple-tab-span" style="white-space: pre;"> </span><a href="mailto:rlhamil@smart.net" class="">mailto:rlhamil@smart.net</a></div><div><br class=""></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""></div></body></html>