<br><br><div><span class="gmail_quote">On 11/21/07, <b class="gmail_sendername">Alexy Khrabrov</b> <<a href="mailto:deliverable@gmail.com">deliverable@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
After the scare of spurious libgcc getting in the way, I'm wondering<br>how can we verify our setups. This is when rpm-style verification<br>and binary distros shine. Sure you can compile stuff, but what if<br>some crap got into your PATH -- beginning with a wrong gcc? What if
<br>some other crap got into LDFLAGS or DYLD_LIBRARY_PATH or whatever?<br>What tools are there to verify<br><br>-- completeness of each port<br>-- proper chain of dependencies of each port<br>-- checking that no port depends on any package not built by the
<br>ports -- e.g., nothing outside /opt/local<br>-- that each executable in /opt/local/bin will load<br>-- what else?<br></blockquote></div><div><br class="webkit-block-placeholder"></div>sounds like you have a fine project scoped out there ;-)
<br clear="all"><br>-- <br>Paul Beard / <a href="http://www.paulbeard.org/">www.paulbeard.org/</a><br><<a href="http://paulbeard@gmail.com/paulbeard@mac.com">paulbeard@gmail.com/paulbeard@mac.com</a>><br>