On Wed, Nov 2, 2011 at 9:25 AM, Phillip Moore <[email protected]> wrote: > I've decided to give up on dependency auditing in the efs-core for a variety > of reasons. > First and foremost, efs-core can only audit a very small subset of the > possible dependencies that can exist in a release, and because these audits > are run on one of the many possible supported platforms, even those audits > can't be done universally. With the introduction of support for XCOFF > (AIX), the fact that we can only audit shared library dependencies in ELF > files makes the coverage of this audit even smaller. > I'm doing two things in parallel right now. First, I'm *finally* making > the "verify" step in the efsdeploy workflow do something. This new sanity > check will make sure that the ELF/XCOFF files actually have the correct > RUNPATH/LIBPATH, and that they are finding their dependent libraries are > expected. This will be run as part of the build and deploy process, where > we can easily perform these sanity checks on each platform natively. That > is FAR more scalable.
This will be a good thing. I've seen binaries end up with the wrong RPATH for several reasons and ended up writing a separate hook to check for that. > Second, I'm making the list of audits performed by the efs-core a parameter, > and will keep the default the same as it currently is. This will allow me > to turn off the dependency audit by changing a parameter, and people who > disagree with me can just keep it there. Complete backwards compatibility, > however, I have no intention of developing the efs-core dependency audits > any further. efsdeploy, of the build system in general, is a much better > place to solve this problem. Keeping the checking as a parameter in efs-core is good. Steven _______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
