Opened 11 years ago
Last modified 11 years ago
#43574 new submission
[NEW] honeysnap
Reported by: | jul_bsd@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | honeysnap |
Description
command-line tool for parsing single or multiple pcap data files and producing a 'first-cut' analysis report that identifies significant events within the processed data
Attachments (1)
Change History (3)
comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 11 years ago by jul_bsd@…
- fix indent
- oups, forgot this one
- 2.x was just because it depends on variant. I added symlink in ${prefix}/bin
- fix variant description
- does the order matter ? alphabetical or reverse?
Changed 10 years ago by jul_bsd@…
Note: See
TracTickets for help on using
tickets.
Thanks, but this does not appear to be ready to commit yet.
However that file does not exist:
Here's what does exist:
The port should probably create a symlink ${prefix}/bin/honeysnap pointing to wherever the file got installed, to make it easier for the user to run it. If the other two programs are ones a user would want to run, then symlinks should be created for them too.
The variant descriptions describe that they will build e.g. "Python 2.7 bindings", but this sounds like the software actually requires python itself; it's not just bindings. The description should be changed, e.g. to "Use Python 2.7".
I would be inclined to change the order in which the variants are defined, the order in which their conflicts are listed, and the order in which the variants are checked before setting the default variant, to alphabetical order.