From owner-freebsd-ports@FreeBSD.ORG Mon Oct 28 14:56:51 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 1718F70D; Mon, 28 Oct 2013 14:56:51 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7EA7D24DD; Mon, 28 Oct 2013 14:56:50 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id c11so6758387wgh.14 for ; Mon, 28 Oct 2013 07:56:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=ds6WakPsRFbLVN4N5mkU4OOinAuB+warO92amNveNng=; b=VHVxgfqxZTvA8OMPf6cpeQeLziTjYIC2lInlW8bUjyd+MC1Z7xE6v0qsgnAyzK+Avf F1i4OU7mRS5Zwygau2Wc0QquJewjy6GKAhLLccUebH9sM+N2rpTsCLbV8OCelpcvxcvv NHfjLbFU5XAEWLHlhVqgvpI0gfBXQFmYfZArLpHPcJdfxeCGyTcog4PkYSibi7+e6UNR WVfxEujBoF+BxxrUM8NG16v8Yfk6zaSEYRjhNNdiHwLBqbbNYvcvwhFD51H9miaCZ/Pw ZDRzEVXyD0/BnOucbNJ7hMJEUHqHkuaCh4uHNfLlzuI7G3pPtAd6n1GJrfNTyiWuiMcm c8FQ== X-Received: by 10.194.185.73 with SMTP id fa9mr18841456wjc.29.1382972208993; Mon, 28 Oct 2013 07:56:48 -0700 (PDT) Received: from ithaqua.etoilebsd.net (ithaqua.etoilebsd.net. [37.59.37.188]) by mx.google.com with ESMTPSA id y20sm36605169wib.0.2013.10.28.07.56.47 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 28 Oct 2013 07:56:48 -0700 (PDT) Sender: Baptiste Daroussin Date: Mon, 28 Oct 2013 15:56:46 +0100 From: Baptiste Daroussin To: Dominic Fandrey Subject: Re: State of the Porters' Handbook Message-ID: <20131028145645.GE74512@ithaqua.etoilebsd.net> References: <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> <526E3986.7050304@bsdforen.de> <526E3BC2.6030004@marino.st> <526E3F32.2040704@bsdforen.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Lb0e7rgc7IsuDeGj" Content-Disposition: inline In-Reply-To: <526E3F32.2040704@bsdforen.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@freebsd.org, marino@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 14:56:51 -0000 --Lb0e7rgc7IsuDeGj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 28, 2013 at 11:40:50AM +0100, Dominic Fandrey wrote: > On 28/10/2013 11:26, John Marino wrote: > > On 10/28/2013 11:16, Dominic Fandrey wrote: > >> On 28/10/2013 11:03, John Marino wrote: > >>> 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 director= ies > >>> properly. > >> > >> Stage replaceses strings in installed files? > >=20 > > No, the port does that kind of thing in the stage directory. After > > everything is installed there in the stage directory, they are packaged > > or installed into the $PREFIX > >=20 > >> I can see the benefits for less error prone package building. But righ= t now > >> it's just additional work coming my way. > >=20 > > You really need to get a better grasp of the concept. There are several > > emails from bapt that may help. For new ports it's not "additional" > > work and for existing ports, yes there is a conversion but the benefits > > are worth it. > >=20 > >>> 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. > >=20 > > Fine, but it's a huge topic that somebody has to write and validate. > > You're willing to criticize (justified) but unwilling to help rectify > > the problem. >=20 > Well, bsd.stage.mk isn't well commented either. I think right now only > the person who implemented it could write reasonable documentation. >=20 > > If you only want to complain, I think you've made your > > point (a point that everyone is already aware of). > >=20 > > FYI, I have no dog in the hunt other than I believe stage is a welcome > > update to ports. >=20 > 1. Implementation > 2. Testing > 3. Documentation > 4. Mandatory >=20 > We're in stage 2 and it's already mandatory. I'm not against staging, > I'm against making things prematurely mandatory. With that kind of reasoning we get the ports tree we have now. Meaning a pi= le of inconsistent, inefficient things, and things like UNIQUENAME not being UNIQ= UE etc. the stage work is a 3 years work almost, that has been half abandonned, a l= ot of time. Documentation on how to convert has been done on the wiki before making sta= ging mandatory and completed since. Documentation for the handbook is another beast because the whole handbook = as to be touched and reviewed, and I ask a couple of time to people to help me documenting on the handbook. I don't buy the opinion that the handbook is totally outdated, all the feat= ures I added but stage are in the handbook including shebang fix ! so perhaps th= at can be improved but that is there. Before committing the stage support I made sure that all previous things has been documented. and sorry but my priority is to have the ports tree back into a sane state = where we have consistency and sane packages, do documentation has much as I can a= nd I try to avoid having too much latency for documentation. Bapt --Lb0e7rgc7IsuDeGj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlJuey0ACgkQ8kTtMUmk6EycrwCgpg54rXirvs0eZy5UK8ik2HLb WrQAn3+8eWaifpY3vppgTmjuKP8xbuvq =gWZs -----END PGP SIGNATURE----- --Lb0e7rgc7IsuDeGj--