From owner-freebsd-ports@FreeBSD.ORG Sat Jul 5 01:13:43 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 A94C475E for ; Sat, 5 Jul 2014 01:13:43 +0000 (UTC) Received: from chilled.skew.org (chilled.skew.org [70.90.116.205]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.skew.org", Issuer "AlphaSSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 72A6225D2 for ; Sat, 5 Jul 2014 01:13:42 +0000 (UTC) Received: from chilled.skew.org (localhost [127.0.0.1]) by chilled.skew.org (8.14.7/8.14.7) with ESMTP id s65101wF007743 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Jul 2014 19:00:01 -0600 (MDT) (envelope-from mike@chilled.skew.org) Received: (from mike@localhost) by chilled.skew.org (8.14.7/8.14.7/Submit) id s651010v007738; Fri, 4 Jul 2014 19:00:01 -0600 (MDT) (envelope-from mike) From: Mike Brown Message-Id: <201407050100.s651010v007738@chilled.skew.org> Subject: Re: Some suggestions about PKGNG documentation In-Reply-To: <53B5868B.4050001@astart.com> To: papowell@astart.com Date: Fri, 4 Jul 2014 19:00:00 -0600 (MDT) X-Whoa: whoa. X-Mailer: ELM [version 2.4ME+ PL126 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jul 2014 01:13:43 -0000 Patrick Powell wrote: > TUTORIAL: The Savant's Guide To Ports, Packages, PkgNG > Try to put a lot of the information about pkgng, repositories, > etc. in a single place. I suggest a tutorial format, rather > than a user manual format, with references to the various > man pages, other documents, etc. Your suggestions sound good to me. Unfortunately, it's not like there's a team of tech writers sitting around waiting for suggestions of things to write and put into the docs. Rather, updating pretty much anything in the documentation -- or the ports for that matter -- requires "suggesting" the actual changes you want in the form of patches that replace the existing content with your version. http://lists.freebsd.org/mailman/listinfo/freebsd-doc http://www.freebsd.org/docproj/ http://www.freebsd.org/doc/en/books/fdp-primer/book.html After starting down this road, you may decide it's less of an ordeal just to write something yourself and put it up on your own blog. :/