<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><blockquote type="cite" class=""><div class="">Le 19 avr. 2021 à 16:47, Karl-Michael Schindler <<a href="mailto:karl-michael.schindler@physik.uni-halle.de" class="">karl-michael.schindler@physik.uni-halle.de</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: FiraCode-Regular; 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; float: none; display: inline !important;" class="">My next steps is to write to them. </span></div></blockquote><div><br class=""></div><div>That's something that each port maintainers could do with their upstream maintainers. </div><div><br class=""></div><div>From my experience, upstream maintainers are happy to help if, in addition to code and test patches, you _contribute documentation/wiki/website patches_ to mention MacPorts.</div><br class=""><blockquote type="cite" class=""><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: FiraCode-Regular; 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; float: none; display: inline !important;" class="">I also want to extent the maintainer part of the docs with the direct to port maintainer to check upstream download and install pages.</span></div></blockquote></div><br class=""><div class="">The MacPorts PR checklist on GitHub could also include something like:</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space: pre;"> </span>[ ] If applicable, ensure that the upstream documentation has MacPorts installation instructions.</div><div class=""><br class=""></div><div class="">Speaking of the PR checklist, the "Tested On" section could include the architecture name:</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>echo "macOS $(sw_vers -productVersion) $(sw_vers -buildVersion) on $(uname -m)"</div><div class=""><br class=""></div><div class="">As I'm now testing both on x86_64 and arm64, that's something I try to include in my PRs...</div><div class=""><br class=""></div><div class="">G.</div></body></html>