Date: Tue, 24 Jul 2007 00:03:25 +0800 From: chinsan <chinsan.tw@gmail.com> To: "Andy Kosela" <andy.kosela@gmail.com> Cc: freebsd-doc@freebsd.org, Doug Barton <dougb@freebsd.org> Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml Message-ID: <1f27304c0707230903i4797a7eekeb91914cd9e2cc9a@mail.gmail.com> In-Reply-To: <3cc535c80707220805i1a7acafapeb547c728ad5e5d8@mail.gmail.com> References: <3cc535c80707220805i1a7acafapeb547c728ad5e5d8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/22/07, Andy Kosela <andy.kosela@gmail.com> wrote: > I see that chinsan's commit generated some confusion and sparked a > discussion about > the overall goals of this chapter. Fist of all it wasn't me who > submitted this new paragraph but I was asked by chinsan to write > something on bpkg(8), because he wanted to include information about > bpkg(8) in the Handbook. Yes. :) > As Marc politely remarked the only "semi-official" tool is > portupgrade(1) and I fully agree with him it should be the only one > fully documented in the Handbook. I don't see any reason to include an > additional nearly identical manual for portmanager (with all due > respect to its creator). But at the same time I agree with Doug here > when he says about the idea of creating a list of actively maintained > ports management applications with a description of each. Letting the > community know the alternatives is a good thing IMHO. Maybe the new article will titled as "The Alternatives of FreeBSD Ports Collection's Management" or something else. :p And It will allow the other ports(ports-mgmt) could be added into here. > Chinsan, Doug - will you be working on this? I am willing to offer my > help if needed. Yes, Sure. I will continuing to work on this. ;-) Cheers, - chinsan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1f27304c0707230903i4797a7eekeb91914cd9e2cc9a>