<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="">Hi,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 13 May 2020, at 3:05 pm, Jason Liu <<a href="mailto:jasonliu@umich.edu" class="">jasonliu@umich.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Maybe it would be better to start by submitting one PR for one isolated port. We can then give you feedback on anything that might need to be changed and merge it. This may enable you to make similar changes in your other ports before submitting them. Then submit a PR for a second port. At some point, once your PRs are getting accepted with no changes, you could submit two or more ports together in a single PR, if the ports are similar and not too complex<br class=""></blockquote><div dir="ltr" class=""><br class=""></div><div class="">Actually I already started the process more than a week ago. The first library, Partio, was accepted and merged yesterday:</div><div class=""><br class=""></div><div class=""><a href="https://github.com/macports/macports-ports/pull/7006" target="_blank" class="">https://github.com/macports/macports-ports/pull/7006</a><br class=""></div><div class=""><br class=""></div><div class="">But of course, Open Shading Language (OSL), the library that depends on Partio, failed the Travis CI build, since Partio didn't exist in the ports tree when I submitted it at the same time:</div><div class=""><br class=""></div><div class=""><a href="https://github.com/macports/macports-ports/pull/7007" target="_blank" class="">https://github.com/macports/macports-ports/pull/7007</a><br class=""></div><div class=""><br class=""></div><div class="">This is what prompted me to write my original question, because it seems that a piece of software like Blender which has a complex dependency tree could potentially take weeks or months for all of the new libraries to get accepted into MacPorts.</div></div></div></div></div></div></div></blockquote><br class=""></div><div>That might well be true I am afraid. The point though is simply putting all the changes into a single PR will not help. If anything it makes it worse as large PRs with a lot of changes are harder to review. Smaller bitesize pieces are much easier to deal with, one step at a time.</div><div><br class=""></div><div>Chris</div><br class=""></body></html>