From owner-freebsd-ports@FreeBSD.ORG Mon Oct 28 10:16:40 2013 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D3490B40; Mon, 28 Oct 2013 10:16:40 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id 6731A212A; Mon, 28 Oct 2013 10:16:39 +0000 (UTC) Received: from mobileKamikaze.norad (MN-VPN2.HS-Karlsruhe.DE [193.196.117.63]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id 39C097E8B4; Mon, 28 Oct 2013 11:16:38 +0100 (CET) Message-ID: <526E3986.7050304@bsdforen.de> Date: Mon, 28 Oct 2013 11:16:38 +0100 From: Dominic Fandrey MIME-Version: 1.0 To: marino@freebsd.org Subject: Re: State of the Porters' Handbook References: <526E234F.3090005@bsdforen.de> <526E2492.9080107@wasikowski.net> <526E2600.9010409@bsdforen.de> <526E272D.3040607@marino.st> <526E2E8D.3020109@bsdforen.de> <526E2FB8.5060906@marino.st> <526E3454.60501@bsdforen.de> <526E3685.4070306@marino.st> In-Reply-To: <526E3685.4070306@marino.st> Content-Type: text/plain; charset=ascii Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, lukasz@wasikowski.net X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Oct 2013 10:16:40 -0000 On 28/10/2013 11:03, John Marino wrote: > On 10/28/2013 10:54, Dominic Fandrey wrote: >> On 28/10/2013 10:34, John Marino wrote: >>> On 10/28/2013 10:29, Dominic Fandrey wrote: >>>> >>>> That's a handfull. What about installers that hard-code directories >>>> during install? >>> >>> They can hardcode into the stage directory. Anywhere else is wrong and >>> has to be fixed. >> >> But then they won't be usable once installed into /usr/local. > > If there are files in those directories, they'll be on the plist and > stage handles them. I'd have to look up how to create empty directories > properly. Stage replaceses strings in installed files? >>>>> You don't have a choice with supporting stage -- new ports without stage >>>>> aren't accepted. So that's why you have to bother. :) >>>> >>>> That doesn't sound acceptable, considering the feature isn't even >>>> mentioned in the Porters' Handbook. >>> >>> Bapt has made several calls for help to document this in the Porters >>> Handbook. He's said it's on his plate but he's behind and has asked for >>> the help. Maybe you could help him out? >> >> So far I see stage as a problem, not something I want to advance. > > I don't know how to respond to this. > 1. It indicates that don't understand the benefits, nor that it's 5 > years overdue, nor that its sorely needed I can see the benefits for less error prone package building. But right now it's just additional work coming my way. > 2. Stage is not going away. There is not another option. > 3. You've been given a source of documentation. It's not in the > handbook, but it does exist in some form. What more do you need to > progress? There is a procedure. Stuff belongs into the handbook. Stick to it. -- 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?