Doorman has issues with the pcap library. Patches have been suggested, but the developer is apparently unavailable. I am marking this port as BROKEN while I try one last attempt to contact the developer. If that fails, I will remove the port. >How-To-Repeat: <code/input/activities to reproduce the problem (multiple lines)>
On Sunday, 2005-05-22 at 12:53:55 -0600, Aaron Dalton wrote: > >Description: > Doorman has issues with the pcap library. Patches have been suggested, > but the developer is apparently unavailable. I am marking this port as > BROKEN while I try one last attempt to contact the developer. If that > fails, I will remove the port. As I've already invested some time in making the daemon run on FreeBSD, I would be willing to take the port. I also had problems getting replies from both the original developer, Bruce Ward (one reply), and the port maintainer, aaron@daltons.ca (none). Before I take on the port, I would rather check back with Bruce to see if doorman is still in active development. Lupe Christoph -- | lupe@lupe-christoph.de | http://www.lupe-christoph.de/ | | Ask not what your computer can do for you | | ask what you can do for your computer. |
Lupe Christoph wrote: > > As I've already invested some time in making the daemon run on FreeBSD, I > would be willing to take the port. I also had problems getting replies > from both the original developer, Bruce Ward (one reply), and the > port maintainer, aaron@daltons.ca (none). Before I take on the port, > I would rather check back with Bruce to see if doorman is still in > active development. > > Lupe Christoph Hello, Lupe. This is Aaron Dalton, the current maintainer. I certainly didn't mean to ignore you. I sent replies to Pav (and I thought I sent some to you, but apparently not). I have attached the email I just sent to Bruce, including all of the emails you have sent me in the past. I wish I could be more help. I'm not a C programmer and that's a disadvantage when a port goes awry. Maybe I'll stick to my perl module ports from now on =) You are welcome to take over if you wish. Sure appreciate your time and understanding! Aaron
Ok folks I signed Lupe as a maintainer of the port. Lupe, any commitable patch right now or should I go and mark port BROKEN? -- Pav Lucistnik <pav@oook.cz> <pav@FreeBSD.org> Two sausages are in a frying pan. One says, "Geez, it's hot in here isn't it?" And the other one says, "Aaaaaah! A talking sausage!"
Responsible Changed From-To: freebsd-ports-bugs->pav My food
State Changed From-To: open->closed Port marked IGNORE'd, maintainer (Lupe) promised to send patches when ready.
Lupe Christoph wrote: > On Sunday, 2005-05-22 at 20:20:05 +0000, Aaron Dalton wrote: > > >> Hello, Lupe. This is Aaron Dalton, the current maintainer. I certainly >> didn't mean to ignore you. I sent replies to Pav (and I thought I sent >> some to you, but apparently not). I have attached the email I just sent >> to Bruce, including all of the emails you have sent me in the past. I >> wish I could be more help. I'm not a C programmer and that's a >> disadvantage when a port goes awry. Maybe I'll stick to my perl module >> ports from now on =) You are welcome to take over if you wish. > > > Well, I don't have much spare time, so I would only take on this port if > you are certain you don't want to continue maintaining it. You could > just as well enlist my help if you have a PR you can't tackle because of > your missing C skills. > > I'll leave the decision to you. If you want to drop it, I'll catch it. > > But please at least acknowlege emails and PRs, even if you can't work on > them. > > Thanks, > Lupe Christoph Given everything that's happening for me right now (in the middle of graduate studies) perhaps it would be best if you took this on, since you have the patches worked out. I'm sorry I can't be of more help. Cheers! Aaron