Ok, I updated the dependencies listed bro-pkg.cfg to get the correct bro-pkg and bro.
Are there suggestions about how I should merge this branch into master and not break people installing this on current releases? .Seth On 16 Jul 2019, at 13:36, Jon Siwek wrote: > On Tue, Jul 16, 2019 at 10:14 AM Michael Dopheide <[email protected]> > wrote: >> >> It builds and works for me against master. Should we change the >> bro-pkg/zkg requirement to > 2.0? > > At a glance, I only see a "bro-pkg >=1.5.0" requirement due to use of > `aliases` metadata field. > >> It should be backwards compatible only as far as when all the >> required includes, etc were included in the install tree. Not sure >> how far back that change was made. > > Bro 2.6 is when headers started to get installed such that packages > could be independent from the source-tree, so adding a "bro >=2.6.0" > requirement makes sense to me. > > - Jon -- Seth Hall * Corelight, Inc * www.corelight.com _______________________________________________ zeek-dev mailing list [email protected] http://mailman.icsi.berkeley.edu/mailman/listinfo/zeek-dev
