From owner-freebsd-questions@FreeBSD.ORG Tue Feb 6 15:32:04 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4FD2316A408 for ; Tue, 6 Feb 2007 15:32:04 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 15C4813C491 for ; Tue, 6 Feb 2007 15:32:03 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from vanquish.pgh.priv.collaborativefusion.com (vanquish.pgh.priv.collaborativefusion.com [192.168.2.61]) (SSL: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Tue, 06 Feb 2007 10:32:03 -0500 id 00056414.45C89F73.00003E3A Date: Tue, 6 Feb 2007 10:32:03 -0500 From: Bill Moran To: "Jim Stapleton" Message-Id: <20070206103203.2af028f5.wmoran@collaborativefusion.com> In-Reply-To: <80f4f2b20702060716s72ee39c9j7efc25cb9ea370d3@mail.gmail.com> References: <80f4f2b20702060716s72ee39c9j7efc25cb9ea370d3@mail.gmail.com> Organization: Collaborative Fusion X-Mailer: Sylpheed 2.3.0 (GTK+ 2.10.7; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: I'd like to do my bit to support FreeBSD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2007 15:32:04 -0000 In response to "Jim Stapleton" : > I've found quite a few tricks and techniques for handling FreeBSD's > ports system when things go south. I'd like to add them to the > handbook, adding, lets say "4.5.6 - When Ports Attack". > > OK, really it'd be more along the lines of "4.5.6 - Installing Ports > When Things Go Wrong" > > It would give hints that I've aquired over time from the mailing list, > or my own use: > 1) config-recursive (my most recent gem aquired from you nice people!) > 2) Keeping flag-sets in your make.conf (basically several sets of > CFLAGS/CXXFLAGS, so if something fails, you can quickly try something > else) > 3) How to remove a broken dependancy (read: how to figure the next > port up, the list, and then configure that port to remove the > dependancy) > 4) Rolling back your ports tree to an earlier date or dates, but > globally or one port at a time > 5) determining which step will fix your problem. > > > Now, as far as I know this would requre: > 1) Downloading the doc group of the ports tree to it's own special > directory, keeping the CVS flags in tact - I should be able to do this > 2) Editing the file of interest - trivial beyond belief > 3) ??Generating the file?? Start here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/index.html As you read through that, you'll probably be pleasantly surprised how well organized and automated everything is. I know I was. > 4) ??Submitting the diffs?? Also covered in the above link. Once you've generated your docs (step #3) you can post your modified copy to your personal website and direct people to it to get feedback and suggestions. There's also a dedicated mailing list for the documentation project: http://lists.freebsd.org/mailman/listinfo/freebsd-doc which was very helpful when I was doing my first submits. Thanks for stepping up to help out! -- Bill Moran Collaborative Fusion Inc.