Change wireshark-chmodbpf to not use a constantly-running daemondo process.

[ghosthound]

As is, wireshark-chmodbpf uses daemondo to run a one-time shell script at startup, leaving the daemondo process running after that. See if we can do this another way so that we don't have the always-running daemondo process.

[ra1nb0w]

I re-read the source code of daemondo and the use of startupitem.start and startupitem.stop seems not working as we would like; therefore the only way is to create the plist manually (as I did in the first version just before discovery the macports way). Have you other suggestions?

Anyway, see this question ​https://github.com/macports/macports-ports/commit/c17993addb0c2428d89f821254f951ea4a193a20#diff-a1f0a08853c3c5eedd3f4bf41a0c4303 and next time you should discuss the change with the maintainer.

[ghosthound]

Re: the permissions on the /dev/bpf* files - I'm quite clear that wireshark only needs read permissions and adding write permission opens up the possibility of spoofing, something people may not want to allow. If there are other ports that want to add write permissions, they should do so themselves. Since I am a maintainer of the wireshark-chmodbpf port I didn't worry about discussing it with anyone else.

[ra1nb0w]

There are two maintainers (I am the other one) therefore...
And if this is your reasoning probably you can fix the problem alone ;-)