<div dir="ltr"><div><div><div>Hi,<br><br></div>following a comment on trac, I put all my Portfile through "port lint --nitpick" and fix many small glitches.<br></div>I was also aware of:<br> # port -q contents $p | grep /bin/ | xargs otool -L<br>
</div><div> # plutil -lint */$p/files/*.plist<br><br>Any other commands useful to validate Portfile, patch & co?<br></div><div>Maybe an additional paragraph in <a href="https://guide.macports.org/#development.practices">https://guide.macports.org/#development.practices</a> (there an entry for port lint but no --nitpick, need to refer to man port)<br>
</div><div><br></div><div>Also, it would be useful to have an intermediate commit level where inclusion means compilation on test infrastructure (<a href="https://build.macports.org/">https://build.macports.org/</a>) but not include in "normal" rsync.<br>
</div><div>It would allow more testing than the single machine many people probably have for developping.<br><br></div><div>Another question, is there any wait for a launchd plist or macports startupitem to specify dependency to run? for example, an application depending on its database.<br>
<br></div><div>Any way to avoid that a new macports daemon user regularly starts distnoted/launchd/cfprefsd/mdworker? Apple daemon users seem to not have this problem and it's loading a box for nothing.<br></div><div>
<br></div><div>Thanks a lot.<br>Cheers,<br><br>Julien<br></div><div><br></div></div>