From owner-freebsd-ports@FreeBSD.ORG Fri Apr 11 14:45:11 2008 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B1981065676 for ; Fri, 11 Apr 2008 14:45:11 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.10.49]) by mx1.freebsd.org (Postfix) with ESMTP id 73E458FC19 for ; Fri, 11 Apr 2008 14:45:11 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd65257.utdallas.edu (utd65257.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTP id AB6166550F for ; Fri, 11 Apr 2008 09:18:53 -0500 (CDT) Date: Fri, 11 Apr 2008 09:18:53 -0500 From: Paul Schmehl To: ports@freebsd.org Message-ID: <0515FD4A165B9F35FA7E1B75@utd65257.utdallas.edu> In-Reply-To: References: X-Mailer: Mulberry/4.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: Ports Request: OpenNMS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2008 14:45:11 -0000 --On Friday, April 11, 2008 09:34:25 -0400 Paul Pathiakis wrote: > > This is another request for someone to port OpenNMS to a FreeBSD port. > > www.opennms.org > > This is a work of art that is well worthwhile beyond Tivoli and > HP-Openview. > > It performs a lot of functions and would be well worth packaging as a > port. There's a lot of people using it, but having it as a port would > be great. > > (No, I don't have time to perform and maintain a port) > And you think we maintainers do? Get real! I just spent several intense evenings/nights updating a complex set of ports that I maintain. I gave up a lot of other things that I could have been doing to do this. I'm not complaining. I volunteered But seriously, this is a community. Ports should be created and maintained by people who actually use them. Otherwise they don't get thoroughly tested and they're more likely to get dropped in the laps of the port team, none of whom are sitting around twiddling their thumbs. In the case of OpenNMS, the build requires jicmp, jrrd and iplike, *none* of which are ported (as well as postgresql, apache-tomcat. java jdk and optionally rddtool, all of which are already ported.) So, to even *start* porting OpenNSM, you would *first* have to port all three of those apps. (And I haven't even looked to see what dependencies *they* have that might not be in the ports tree yet. This is not uncommon with complex software packages. In fact, the ports that I just submitted updates for *forced* me to port three other apps *first*, just so I could port what *I* wanted. (And yes, I maintain those as well.) If you're really serious that you want OpenNMS ported, then it's time to make your contribution to FreeBSD. :-) Solicit help from other FreeBSD users who use/want OpenNMS, and work together to distribute the load and get the job done. There's plenty of people on this list who can help you when you run into problems. -- Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/