[Bro-Dev] New documentation via Sphinx

I'm in the process of documenting Broker with Sphinx. With minimal effort, I put up a scaffold that looks like this: http://bro.github.io/broker/ It's the bootstrap theme for sphinx, as an alternative to the classic read-the-docs theme. I've hacked the sidebar so that it shows the table of

Re: [Bro-Dev] package manager progress

> On Jul 27, 2016, at 12:15 PM, Johanna Amann wrote: > > And to add a me three to this - I am also with him on this one. On top of > things - I might misremember this, but didn't we plan package names to > include the github user name at one point of time? So a package name

Re: [Bro-Dev] package manager progress

On Sun, Jul 24, 2016 at 19:45 +, you wrote: > The package manager client is at a point now where I think it would be > usable. Finally got a chance to play with it a bit. Excellent work, I really like it! Belows a list of just smaller things I noticed. The only larger question I have is

Re: [Bro-Dev] package manager progress

> On Jul 27, 2016, at 12:59 PM, Robin Sommer wrote: > > Ah, I see. Would it be better to generally use the full path as the > name, and not search for submatches, to make it consistent/unambiguous > what a name refers to? At least from my usage it’s been convenient to be able

Re: [Bro-Dev] package manager progress

Make it four. :) I'm with Seth, too, better not to enforce any naming scheme because the boundaries are unclear. Also, note that a single binary Bro plugin can provide multiple quite different things (say, a reader and an analyzer and a packet source all at the same time, if one so desires :).

Re: [Bro-Dev] package manager progress

> On Jul 27, 2016, at 11:15 AM, Johanna Amann wrote: > > And to add a me three to this - I am also with him on this one. On top > of things - I might misremember this, but didn't we plan package names > to include the github user name at one point of time? So a package name

Re: [Bro-Dev] package manager progress

And to add a me three to this - I am also with him on this one. On top of things - I might misremember this, but didn't we plan package names to include the github user name at one point of time? So a package name would be user/redis, for example, and there also could be user2/redis? Johanna

Re: [Bro-Dev] package manager progress

> I actually don't like this that much because some of these can cross > boundaries and do all sorts of different things in a single plugin. > It makes more sense to me to leave the naming open. I'm with Seth on this one. The reason why I think we should keep the naming open is that it's the

Re: [Bro-Dev] package manager progress

> On Jul 27, 2016, at 11:44 AM, Seth Hall wrote: > > >> On Jul 25, 2016, at 4:49 PM, Azoff, Justin S wrote: >> >> In one aspect the pktsrc- prefix acts like a tag, but can also help >> disambiguate plugins... i.e., a redis log writer plugin vs. a redis

Re: [Bro-Dev] package manager progress

> On Jul 25, 2016, at 4:49 PM, Azoff, Justin S wrote: > > In one aspect the pktsrc- prefix acts like a tag, but can also help > disambiguate plugins... i.e., a redis log writer plugin vs. a redis data > store plugin vs. a redis protocol analyzer. I actually don't like