[Bro] Bro updates force some bro-pkg rebuilds.. sometimes.

Mike Dopheide dopheide at gmail.com
Wed Feb 28 12:27:44 PST 2018

I'm sure others have experienced this, when updating Bro, packages with C++
components will need to be re-installed/rebuilt (sometimes, not always).
There may be some crazy C++ way of avoiding that, but outside of that I've
been trying to come up with options to suggest so our upgrade process can
be more easily automated.

What do folks think about a couple options to bro-pkg such as:
1) a new package.meta file field:
2) And a corresponding bro-pkg command:  bro-pkg rebuild [nodeps]

Separately, but kinda related, I wouldn't mind a '--yes' flag or something
similar when packages aren't being installed interactively.

Alternatively, the idea has been tossed around that we build the bro
packages we use into RPMs, but then that sorta defeats the bro-pkg command

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/bro/attachments/20180228/8a1bdb79/attachment.html 

More information about the Bro mailing list