<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, Mar 2, 2017 at 9:19 AM Siwek, Jon <<a href="mailto:jsiwek@illinois.edu">jsiwek@illinois.edu</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In other words, I think bro-pkg is already set up to handle distributing pre-built binary plugins, but the more difficult problems to address will relate to how to actually produce plugins that will be binary-compatible w/ a user’s Bro installation. E.g. lack of stable/standard ABI in Bro and C++ itself means there’s myriad ways to produce unportable binaries.<br class="gmail_msg"></blockquote><div><br></div><div>This, I think, is the big gotcha. Different linux distros, different compilers, different libraries. It even goes into which version of boost is used. There's also matching to the version of Bro whether that's master or release N. </div><div><br></div><div>I'm trying to come up with parallels with the Linux kernel. Loadable modules have vermagic and there's DKMS. Neither fully covers the breadth of issues that can occur. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="gmail_msg">
The only other idea I have, is if bro-pkg is not able to locate Bro source code (i.e. the user installed Bro from a binary package), then it could automatically download the appropriate version (e.g. clone Bro’s git repo and checkout a specific version tag).<br class="gmail_msg"></blockquote><div><br></div><div>From a deployment perspective, there really shouldn't be a compiler on the system running a deployed Bro. Even further, the system might be limited on where on the internet it can reach. At least with many of our customers, that's the case. </div><div><br></div><div> ...alan</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="gmail_msg">
- Jon<br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
bro-dev mailing list<br class="gmail_msg">
<a href="mailto:bro-dev@bro.org" class="gmail_msg" target="_blank">bro-dev@bro.org</a><br class="gmail_msg">
<a href="http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev</a><br class="gmail_msg">
</blockquote></div></div>