From owner-freebsd-ports@FreeBSD.ORG Wed Jan 15 22:29:38 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2C257E3E for ; Wed, 15 Jan 2014 22:29:38 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 028711D47 for ; Wed, 15 Jan 2014 22:29:35 +0000 (UTC) Received: from [192.168.0.21] (unknown [130.255.19.191]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id B3CFD43552; Wed, 15 Jan 2014 16:29:18 -0600 (CST) Message-ID: <52D70BAD.7080601@marino.st> Date: Wed, 15 Jan 2014 23:29:01 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Maxim Sirenko Subject: Re: FreeBSD Port: abills-0.54 References: <52D6F34A.9020900@rivne.uar.net> <52D70A62.8030608@rivne.uar.net> In-Reply-To: <52D70A62.8030608@rivne.uar.net> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "freebsd-ports@freebsd.org" , Mikhail Tsatsenko X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: marino@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jan 2014 22:29:38 -0000 On 1/15/2014 23:23, Maxim Sirenko wrote: > ))) > OK > I can't do that -- not enough knowledge & experience. > I thought the author maintains the port. > > Good Luck! > The port is unmaintained, as seen in the second line of its description: http://www.freshports.org/net/abills/ The means the most probable way it will get an update is if a user submits an update via a PR. Even then, chances are the PR wouldn't get picked up right away due to very large backlog. You'd have to "sell" why that port should get attention before the rest (and being only 0.01 versions away from the most recent version doesn't sound bad). John