From owner-freebsd-doc@FreeBSD.ORG Thu Sep 22 20:50:39 2005 Return-Path: X-Original-To: freebsd-doc@freebsd.org Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 072B716A41F for ; Thu, 22 Sep 2005 20:50:39 +0000 (GMT) (envelope-from josh@tcbug.org) Received: from rwcrmhc12.comcast.net (rwcrmhc14.comcast.net [216.148.227.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id C23AF43D45 for ; Thu, 22 Sep 2005 20:50:38 +0000 (GMT) (envelope-from josh@tcbug.org) Received: from [192.168.1.102] (c-24-118-173-219.hsd1.mn.comcast.net[24.118.173.219]) by comcast.net (rwcrmhc14) with ESMTP id <2005092220503601400okhk6e>; Thu, 22 Sep 2005 20:50:37 +0000 From: Josh Paetzel To: Giorgos Keramidas Date: Thu, 22 Sep 2005 15:51:42 -0500 User-Agent: KMail/1.8.1 References: <200509211504.46861.josh@tcbug.org> <20050922002217.GA24457@soaustin.net> <20050922020313.GA1376@flame.pc> In-Reply-To: <20050922020313.GA1376@flame.pc> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509221551.43003.josh@tcbug.org> Cc: Mark Linimon , freebsd-doc@freebsd.org Subject: Re: Proposed addition to the handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2005 20:50:39 -0000 On Wednesday 21 September 2005 21:03, Giorgos Keramidas wrote: > On 2005-09-21 19:22, Mark Linimon wrote: > >On Wed, Sep 21, 2005 at 03:04:46PM -0500, Josh Paetzel wrote: > >> Another question would be if this would go beyond the 'basic > >> instructions' statement at the top of the page. > > > > There is a lot of information that is IMHO missing on the various > > strategies to keep up with and use the Ports Collection > > (portupgrade, cvsup, and portsnap all deserve their own > > sections). There is a little bit at the end of the Porter's > > Handbook but IMHO the PH is too large anyways, and ought to be > > reoriented into just something targeted at maintainers. > > > > What do people think: should this information be in some kind of > > expanded section in the Handbook? Or a separate Article? > > I'm always in favor of splitting the documentation to at least > three types of documents: > > - Administrator documentation > - End-user documentation > - Developer documentation > > So, I'm in favor of keeping this out of the Porter's Handbook, > which should orbit ever closer to the third type (developer docs). > > - Giorgos I will start on the document, perhaps as it evolves it will be clearer as to where to put it. -- Thanks, Josh Paetzel