From owner-svn-ports-head@freebsd.org Fri Apr 8 19:41:34 2016 Return-Path: Delivered-To: svn-ports-head@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 63C5DB08B07; Fri, 8 Apr 2016 19:41:34 +0000 (UTC) (envelope-from pi@FreeBSD.org) Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4]) (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 24B1910AF; Fri, 8 Apr 2016 19:41:34 +0000 (UTC) (envelope-from pi@FreeBSD.org) Received: from pi by fc.opsec.eu with local (Exim 4.86_2 (FreeBSD)) (envelope-from ) id 1aocHX-000Oky-8y; Fri, 08 Apr 2016 21:41:27 +0200 Date: Fri, 8 Apr 2016 21:41:27 +0200 From: Kurt Jaeger To: Torsten Zuehlsdorff Cc: Sunpoet Po-Chuan Hsieh , Kurt Jaeger , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r412678 - in head/mail: . rubygem-premailer Message-ID: <20160408194127.GK991@fc.opsec.eu> References: <201604071804.u37I4JHi070885@repo.freebsd.org> <57080915.1010604@toco-domains.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57080915.1010604@toco-domains.de> X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2016 19:41:34 -0000 Hi! > > Most rubygem ports use RUBYGEM_AUTOPLIST (and PLIST_FILES if necessary). > > Is there any reason to use pkg-plist instead here? I did not knew about RUBYGEM_AUTOPLIST. > It is because of bin/premailer, which RUBYGEM_AUTOPLIST seems to ignore. > If there is a way to keep the AUTOPLIST this would be fine. There is: Using RUBYGEM_AUTOPLIST and PLIST_FILES for bin/premailer works. -- pi@FreeBSD.org +49 171 3101372 4 years to go !