Date: Wed, 31 Aug 2016 13:42:31 +0200 From: Stanislaw Halik <sthalik@tehran.lain.pl> To: Kurt Jaeger <lists@opsec.eu>, Stanislaw Halik <sthalik@tehran.lain.pl> Cc: "James A. McGuire" <j.a.mcguire@gmail.com>, ports@freebsd.org Subject: Re: FreeBSD Port: noip-2.1.9_3 Message-ID: <a8a8d7fc-896b-ebf0-0bd8-26a2329979bc@misaki.pl> In-Reply-To: <20160831113651.GF96200@home.opsec.eu> References: <CADPthFdUyAGUMpPpAJ16g8W_mR_RkYsWF4BezjkWC2k5aW0j1g@mail.gmail.com> <8d22b341-b1ec-f2b9-d7e0-61564bdb8bb2@misaki.pl> <20160831113651.GF96200@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
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. sh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a8a8d7fc-896b-ebf0-0bd8-26a2329979bc>