Date: Mon, 20 Mar 2017 15:39:25 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Torsten Zuehlsdorff <tz@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r436543 - in head/net: . rubygem-signet Message-ID: <20170320153925.GA5635@FreeBSD.org> In-Reply-To: <92ad0276-2ad6-cd53-6774-162fe9aa6cf0@FreeBSD.org> References: <201703201357.v2KDvKfK044369@repo.freebsd.org> <20170320140048.GA3711@FreeBSD.org> <92ad0276-2ad6-cd53-6774-162fe9aa6cf0@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 20, 2017 at 03:06:29PM +0100, Torsten Zuehlsdorff wrote: > On 20.03.2017 15:00, Alexey Dokuchaev wrote: > > On Mon, Mar 20, 2017 at 01:57:20PM +0000, Torsten Zuehlsdorff wrote: > >> New Revision: 436543 > >> URL: https://svnweb.freebsd.org/changeset/ports/436543 > >> > >> Log: > >> New port: net/rubygem-signet > >> > >> Signet is an OAuth 1.0 / OAuth 2.0 implementation > >> > >> WWW: https://rubygems.org/gems/signet > >> ... > >> +MAINTAINER= ruby@FreeBSD.org > >> +COMMENT= Signet is an OAuth 1.0 / OAuth 2.0 implementation > > > > Violation of PHB Section 5.6, item #2. > > Can you provide a better solution? Since its all i can found about the > library it was hard to craft a better one. I see; we're dealing with upstream that does not even care to provide different `s.description' and `s.summary' (per signet.gemspec) themselves. What a pity. I guess I hit that `send' button too soon, my apologies. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170320153925.GA5635>