Date: Wed, 15 Jul 2020 09:26:10 +1000 From: Kubilay Kocak <koobs@FreeBSD.org> To: Alexey Dokuchaev <danfe@freebsd.org>, Kurt Jaeger <pi@freebsd.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r542225 - in head/devel: . py-jailconf Message-ID: <499c1738-dce8-939f-02f3-752e06cecf4a@FreeBSD.org> In-Reply-To: <20200714174132.GA44952@FreeBSD.org> References: <202007141709.06EH92Rt066640@repo.freebsd.org> <20200714171722.GA81439@FreeBSD.org> <20200714172653.GA32466@fc.opsec.eu> <20200714174132.GA44952@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15/07/2020 3:41 am, Alexey Dokuchaev wrote: > On Tue, Jul 14, 2020 at 07:26:53PM +0200, Kurt Jaeger wrote: >> ... >> And: There's not much more description for that port anyway, >> so what should be in pkg-descr...? > > In this case, port maintainer or (if maintainer failed to do so) > committer handling the PR should glance over the code and write > up sensible description him/herself. > > Or they might see how packagers in popular GNU/Linux distributions > describe the same or similar package (often works). > > Or they can ask upstream, or talk to someone who's using it, or > just ask for peer review on IRC. > > If all fails, sometimes we do have to resort to one-line port > description. But even in this case, Python should be spelled > correctly. :-) > > ./danfe > I've done the latter (ask upstream) and will adjust pkg-descr in short order on response
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?499c1738-dce8-939f-02f3-752e06cecf4a>