From owner-freebsd-doc@FreeBSD.ORG Fri Jul 20 11:54:53 2007 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DE6116A46C for ; Fri, 20 Jul 2007 11:54:53 +0000 (UTC) (envelope-from chinsan.tw@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id 29CA413C467 for ; Fri, 20 Jul 2007 11:54:53 +0000 (UTC) (envelope-from chinsan.tw@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so209861anc for ; Fri, 20 Jul 2007 04:54:51 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=O257nVSlUn8MNmuLvGRS/vVXgXVGRYzphEdAYMxswJE9mbDzQHdp+XIH/WOHSXMWre9LPbljKymrSiF6GnulOY4mYYD6mDXcpJ6LbIbLkXE+KPW+0yblB5OC8Aqr4Vfwhbr1VuCTFzejZzFllJzBheDzGA4Z0Ve7FCmtsY4pHCo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YfitmZFRlk7hGLrUjdJ99derxihmEAT4Ac0+noq3tXDwy37+RVV4OSYjpJrkUF7CztPFJtnh74QPWVFecSbxcxUb+FZWNH5hDeBVkt1NU/PaWHP31/7Lbagc4hx+ShcacLdSl+2ce8WUpd+dvZPa9cgiUf9S4ZaAwj2UNEPVfvo= Received: by 10.100.47.9 with SMTP id u9mr186567anu.1184932491747; Fri, 20 Jul 2007 04:54:51 -0700 (PDT) Received: by 10.100.119.4 with HTTP; Fri, 20 Jul 2007 04:54:51 -0700 (PDT) Message-ID: <1f27304c0707200454h4b842da7jb2de8327968faee5@mail.gmail.com> Date: Fri, 20 Jul 2007 19:54:51 +0800 From: chinsan To: "Giorgos Keramidas" In-Reply-To: <20070719125410.GA9766@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200707190121.l6J1LOvd007607@repoman.freebsd.org> <20070719054803.GA1002@gothic.blackend.org> <469F1D0F.2090307@FreeBSD.org> <20070719125410.GA9766@kobe.laptop> Cc: freebsd-doc@freebsd.org, doc-committers@freebsd.org, cvs-all@freebsd.org, cvs-doc@freebsd.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml 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: Fri, 20 Jul 2007 11:54:53 -0000 On 7/19/07, Giorgos Keramidas wrote: > On 2007-07-19 01:13, Doug Barton wrote: > >>> en_US.ISO8859-1/books/handbook/ports chapter.sgml > >>> Log: > >>> - Introduce another way for upgrading packages and ports using bpkg(8). > >> > >> I'm not sure the Handbook has the vocation to talk about all > >> available tools to manage ports and packages. [...] > > > > FWIW, I (with portmaster author hat on) am sort of ambivalent about > > this issue. I've avoided adding anything to that chapter about > > portmaster because my personal feeling is that a laundry list of > > tools isn't useful to the user, especially if all the descriptions > > are the same size as the ones that are there now. > > > > What I think would be more useful (and again, I'm speaking only for > > myself) would be a list of tools available with a brief description > > of each, and links to outside sources (web pages, pkg-descr files, > > etc.) where an interested user can get more information. I do think > > that letting our users know that there are tools available is a good > > thing, I don't think mini-manuals for each tool is appropriate in > > that context. > > This sounds nice. > > It would also be nice to have articles like: > > "Managing thirdparty ports & packages with portupgrade" > "Managing thirdparty ports & packages with portmaster" > "Managing thirdparty ports & packages with XXX" > > in the doc/en_US.ISO8859-1/articles/... collection, so the Handbook > can talk about the general, common ideas behind port management, and > the articles can turn into mini-manuals. umm.. good suggestion. I'll revert it back and rewitre a mini article. > > It may even be possible to talk about one or two (the 'official' port > management tools), and then move the rest into separate articles. If > the tools mentioned in the articles get 'official' status or one of > the currently official tools gets dropped, or gets stale, we can move > chunks of the Handbook from articles to the book, or from the book to > standalone articles. Ya, I'm planning to write some iss about port management in the base system.