Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore moving zeek.hh into Zeek #339

Open
J-Gras opened this issue Apr 28, 2023 · 1 comment
Open

Explore moving zeek.hh into Zeek #339

J-Gras opened this issue Apr 28, 2023 · 1 comment

Comments

@J-Gras
Copy link
Contributor

J-Gras commented Apr 28, 2023

@Neverlord pointed out that the zeek.hh could move into Zeek to fully decouple Zeek and broker. As far as I can tell, this would require the python bindings as well as some testing to move as well.

@Neverlord
Copy link
Member

As far as I can tell, this would require the python bindings as well as some testing to move as well.

I wouldn't move the bindings. I'd say this ticket is simply blocked by #303. Once the bindings are gone, there's no technical reason anymore for the zeek.hh header to stay in the Broker code base and we can instead move to over to the Zeek side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants