From owner-freebsd-ports@freebsd.org Wed Oct 11 18:52:39 2017 Return-Path: Delivered-To: freebsd-ports@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 F3190E33A74; Wed, 11 Oct 2017 18:52:38 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7A4772951; Wed, 11 Oct 2017 18:52:38 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id A788FC85; Wed, 11 Oct 2017 13:52:36 -0500 (CDT) Date: Wed, 11 Oct 2017 13:52:35 -0500 From: Mark Linimon To: Russell Haley Cc: Benjamin Kaduk , koobs@freebsd.org, doc@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Porters Handbook section 4.4 Message-ID: <20171011185235.GA7088@lonesome.com> References: <8a3e663a-d94f-0ef7-bbc7-8ebaa111f6dd@FreeBSD.org> <7b2f2464-5c35-e24a-2047-838c1a9e96a3@FreeBSD.org> <20171009224825.GM96685@kduck.kaduk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2017 18:52:39 -0000 I had not commented before because I am on a long road trip. But I'm very glad you have taken on this work. I had always wanted to do something very much like this but never made the time to do it. My old thought was that we have conflated "User's Guide to Ports" and "Ports Reference Handbook". Certainly the bulk of the existing text is the latter type (even if not well organized; it kind of "grew".) I'm indifferent if the Guide parts (basically what you have been working on) remain in the PH or become a separate piece. But depending on the degree of rewrite, do you think that might be easier? It's certainly true that the current PH is too bloated. I won't have the cycles to look at your work for another week or two, so consider this just "a voice from the peanut gallery". mcl