From owner-freebsd-ports@FreeBSD.ORG Fri Apr 11 09:13:36 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7038637F; Fri, 11 Apr 2014 09:13:36 +0000 (UTC) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id D56271C1F; Fri, 11 Apr 2014 09:13:35 +0000 (UTC) Received: from AprilRyan.norad (iz-aix-213a.HS-Karlsruhe.DE [193.196.64.213]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id 9F53685FC4; Fri, 11 Apr 2014 11:13:23 +0200 (CEST) Message-ID: <5347B234.7070902@bsdforen.de> Date: Fri, 11 Apr 2014 11:13:24 +0200 From: Dominic Fandrey User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Baptiste Daroussin Subject: Re: New port, what's next? References: <5346D5AF.5070905@bsdforen.de> <20140410182839.GB29301@ivaldir.etoilebsd.net> In-Reply-To: <20140410182839.GB29301@ivaldir.etoilebsd.net> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ascii Content-Transfer-Encoding: 7bit Cc: Helmut Schneider , freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2014 09:13:36 -0000 On 10/04/2014 20:28, Baptiste Daroussin wrote: > On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: >> >> On 10/04/2014 18:53, Helmut Schneider wrote: >>> I created a new port, Typo3-LTS. The tgz contains >>> >>> - Makefile >>> - distinfo >>> - pkg-plist >>> - pkg-descr >>> - a diff from www/typo3 >>> >>> The file has ~150kB so I assume it's to big for a PR. >> >> I assume the bulk of that is the pkg-plist. The largest pkg-plist >> in the ports tree is 4M. In my opinion huge plists should be dynamically >> generated, but in your case I'd just I'd just temp-host the file >> somewhere and file a PR with a link and a checksum. >> >> Regards >> > > ... > autoplist is dangerous because we have no way to control that what is package is > what the maintainer expect to be packaged! therefore we often end up with > unoticed problems The majority of problems I used to have as a port maintainer stemmed from fiddling with plists. I.e. my experience is the opposite, manual plists lead to errors. Autogenerated plists (which I use in most cases, because dynamic ones are against policy) have reduced the amount of mistakes I make tremendously. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?