On Wed, Nov 2, 2011 at 9:25 AM, Phillip Moore <[email protected]> wrote: > efsdeploy, of the build system in general, is a much better place to solve > this problem You should see both of these patches in the next couple of > weeks, but the > efs-core one's coming first. I have a short term need to get that audit out > of my way, due to how I'm building gnu/gcc now (separate discussion).
So how does this work with this model, with users/developers who do not use efsdeploy at all, to build or engineer their installs into EFS? Java folks, binary vendor products, internally-build projects using their own CI tools, etc.? Does the dependency checking happen by efs-core calling efsdeploy, and feeding that back into the core? Or some other method? In our world, efsdeploy is very minimally used, currently only < ~5% of the products pushed out utilize it. With broader marketing, we may get 20-30%, but we certainly won't get 80+% unless we enforce its use for everyone (not likely). I just want to be sure we're not orphaning off dependency audits to a tool that is not used broadly in the environment. _______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
