From owner-freebsd-ports@FreeBSD.ORG Mon Jan 12 09:06:51 2009 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 999451065670 for ; Mon, 12 Jan 2009 09:06:51 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (megatron.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id 4D7F58FC1A for ; Mon, 12 Jan 2009 09:06:51 +0000 (UTC) (envelope-from mad@madpilot.net) Received: by megatron.madpilot.net (Postfix, from userid 1000) id 1F7DD130C5B; Mon, 12 Jan 2009 09:47:36 +0100 (CET) Date: Mon, 12 Jan 2009 09:47:35 +0100 From: Guido Falsi To: info@rdfund.com Message-ID: <20090112084735.GA68854@megatron.madpilot.net> References: <20090112075422.51823wc9yl0zkawe@webmail.rdfund.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090112075422.51823wc9yl0zkawe@webmail.rdfund.com> X-Operating-System: FreeBSD 7.1-STABLE User-Agent: Mutt/1.5.18 (2008-05-17) Cc: ports@FreeBSD.org Subject: Re: port not maintained properly 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: Mon, 12 Jan 2009 09:06:51 -0000 On Mon, Jan 12, 2009 at 07:54:22AM +0000, info@rdfund.com wrote: > Dear All, > > I am writing you regarding the resin-3.1.5_1 port to freebsd. The > official maintainer boris@tagnet.ru did not release any updates > regardless of numerous mailings both from me and from the owners of the > Caucho Resin project. The last port is for version 3.1.5, however since > then there was one minor and one major update resin 3.1.6 and 3.2.0. (see > www.caucho.com) > > Could you please take the necessary measures so that the resin port is > properly maintained? If you're using it, you could update it to latest version and senda PR about it. If the maintainer times out (after 2 weeks, usually) it will be committed. You should really just try, it's not hard to update an existing port(nor to create a new opne, except for very elaborated pieces of software.) -- Guido Falsi