https://bugzilla.redhat.com/show_bug.cgi?id=1510261

            Bug ID: 1510261
           Summary: Review Request: bro - A network security monitoring
                    and analysis platform
           Product: Fedora
           Version: rawhide
         Component: Package Review
          Severity: medium
          Assignee: nob...@fedoraproject.org
          Reporter: de...@rocknsm.io
        QA Contact: extras...@fedoraproject.org
                CC: package-review@lists.fedoraproject.org



Spec URL:
http://copr-dist-git.fedorainfracloud.org/cgit/@rocknsm/rocknsm-2.1/bro.git/tree/bro.spec?h=f26
SRPM URL:
https://copr-be.cloud.fedoraproject.org/results/@rocknsm/rocknsm-2.1/fedora-26-x86_64/00639439-bro/bro-2.5.2-1.fc26.src.rpm
Description: 

I'd like to submit an update for the current bro package to be included in
Fedora and EPEL. I am a core developer and maintainer of the RockNSM
(http://rocknsm.io) project and I maintain a number of packages for EL7 that
are either custom tools developed for the ROCK project or backports from
Fedora. This is my first package, so I need a sponsor.

I cleaned up a lot of the existing bro package, including fixing some paths and
package dependencies according to how they're actually used. I also introduce a
`bro-devel` package that allows me to build bro plugins without requiring the
full source tree. Admittedly, it's not the most elegant solution, but the way
the cmake build system is used for the bro project, it's the cleanest I could
come up with.

Once I get a good understanding of this process, I have some additional related
packages to submit. capstats needs `setcap` on the binary for example.

Fedora Account System Username: dcode

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- package-review@lists.fedoraproject.org
To unsubscribe send an email to package-review-le...@lists.fedoraproject.org

Reply via email to