Re: [Bro-Dev] bro-devel package?

On Thu, May 24, 2018 at 2:50 PM, Vlad Grigorescu 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 >

Re: [Bro-Dev] bro-devel package?

> On May 24, 2018, at 3:50 PM, Vlad Grigorescu 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

Re: [Bro-Dev] bro-devel package?

Well that’s s great question! Right now my spec for building plugins downloads entire bro tree and does some cmake plugin to avoid waiting for the tree to build. > On May 24, 2018, at 9:50 PM, Vlad Grigorescu wrote: > > There are a couple of cases where I think it'd be useful

[Bro-Dev] bro-devel package?

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

Re: [Bro-Dev] Broker has landed in master, please test

On Wed, May 23, 2018 at 20:16 +, Adam wrote: > I think those question belong on the main list which is for using Bro > and its language. This list is really more about development of Bro > itself. Just to give context here, the reason I sent the original mail about Broker here, including