From owner-freebsd-ports@freebsd.org  Wed Aug 31 11:43:55 2016
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BD40BC9D3E
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Wed, 31 Aug 2016 11:43:55 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id 74463E1F
 for <freebsd-ports@freebsd.org>; Wed, 31 Aug 2016 11:43:55 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 7390DBC9D3D; Wed, 31 Aug 2016 11:43:55 +0000 (UTC)
Delivered-To: ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72F0ABC9D3C
 for <ports@mailman.ysv.freebsd.org>; Wed, 31 Aug 2016 11:43:55 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 34225E17
 for <ports@freebsd.org>; Wed, 31 Aug 2016 11:43:55 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1bf3vu-0007v5-IW; Wed, 31 Aug 2016 13:43:54 +0200
Date: Wed, 31 Aug 2016 13:43:54 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Stanislaw Halik <sthalik@tehran.lain.pl>,
 "James A. McGuire" <j.a.mcguire@gmail.com>, ports@freebsd.org
Subject: Re: FreeBSD Port: noip-2.1.9_3
Message-ID: <20160831114354.GG96200@home.opsec.eu>
References: <CADPthFdUyAGUMpPpAJ16g8W_mR_RkYsWF4BezjkWC2k5aW0j1g@mail.gmail.com>
 <8d22b341-b1ec-f2b9-d7e0-61564bdb8bb2@misaki.pl>
 <20160831113651.GF96200@home.opsec.eu>
 <a8a8d7fc-896b-ebf0-0bd8-26a2329979bc@misaki.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a8a8d7fc-896b-ebf0-0bd8-26a2329979bc@misaki.pl>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2016 11:43:55 -0000

Hi!

> On 2016-08-31 Wed 13:36, Kurt Jaeger wrote:
> >> It can sure be changed with a patch. I'd like however to wait for
> >> someone with ports commit bit to comment as to whether that change lies
> >> within the scope of what the ports tree does. My understanding is that
> >> the ports tree generally doesn't introduce new functionality.
> >
> > I suggest to add that feature with a patch and then submit that
> > change upstream so that upstream adds that feature, too.
> 
> Hey,
> 
> Last upstream update was in 2009. The source tarball's hosted by ehaupt@ 
> since the original URI returns 404.

Then adding the patch is the way to go and asking ehaupt to update
the distfile with the patch...

-- 
pi@opsec.eu            +49 171 3101372                         4 years to go !