> On May 24, 2018, at 3:50 PM, Vlad Grigorescu <[email protected]> wrote: > > There are a couple of cases where I think it'd be useful to have a bro-devel > package -- a package that I can install on a system, and then be able to > build plugins against Bro. (This is the same model as other *-devel packages, > such as openssl, libpcap, etc.) > > Right now, if I compile Bro from source, run make install, I can't build a > package with what's in /usr/local -- Bro needs the entire source tree, since > the required headers are not present in /usr/local. > > I'm curious how people are dealing with this issue, and if anyone has > thoughts on whether this would be useful, and if so, what it would take to > build such a package. >
I ran into this issue in two places: on our infrastructure and working out how to support bro as a language on travis-ci. For our installations I worked around it by just building packages that contain bro plus all the plugins I need and dump the entire thing into a single RPM. This works ok for me, but would never work for something like debian that is probably trying to figure out how to package some of the bro plugins. This also doesn't work for adding bro support for travis.. the OBS RPMs come close.. we can install those plus bro-pkg, but any packages that need to be built against bro won't compile. — Justin Azoff _______________________________________________ bro-dev mailing list [email protected] http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
