From owner-freebsd-ports@FreeBSD.ORG Thu Feb 2 21:25:33 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BD38106564A for ; Thu, 2 Feb 2012 21:25:33 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo103.cox.net (eastrmfepo103.cox.net [68.230.241.215]) by mx1.freebsd.org (Postfix) with ESMTP id C56418FC16 for ; Thu, 2 Feb 2012 21:25:32 +0000 (UTC) Received: from eastrmimpo109.cox.net ([68.230.241.222]) by eastrmfepo103.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20120202212531.CFUO28068.eastrmfepo103.cox.net@eastrmimpo109.cox.net> for ; Thu, 2 Feb 2012 16:25:31 -0500 Received: from serene.no-ip.org ([98.164.86.55]) by eastrmimpo109.cox.net with bizsmtp id V9RX1i00E1BeFqy029RXSN; Thu, 02 Feb 2012 16:25:31 -0500 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020209.4F2AFF4B.0114,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=EYzcOfuzocFB4Uh5a8S+SAtfBMCIXs4UTLohtyR2Crs= c=1 sm=1 a=ojH9cbcSZWsA:10 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=fdHYxQQoAueMHNSmXppgDg==:17 a=pGLkceISAAAA:8 a=kviXuzpPAAAA:8 a=q56oFxeYAAAA:8 a=3nayRcIMsbnvFXdGTsUA:9 a=CjuIK1q_8ugA:10 a=k3S3GY7AwsAA:10 a=MSl-tDqOz04A:10 a=4vB-4DCPJfMA:10 a=fdHYxQQoAueMHNSmXppgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id q12LPVhe049329 for ; Thu, 2 Feb 2012 15:25:31 -0600 (CST) (envelope-from conrads@cox.net) Date: Thu, 2 Feb 2012 15:25:26 -0600 From: "Conrad J. Sabatier" To: freebsd-ports@freebsd.org Message-ID: <20120202152526.54220cfa@cox.net> In-Reply-To: References: <20111203173149.224a64e6@cox.net> <20111214004838.GK1593@dormouse.experts-exchange.com> <20120112212905.GA78819@dormouse.experts-exchange.com> <20120127200325.66f36090@cox.net> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: A new and better way to do "make readmes"? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Feb 2012 21:25:33 -0000 On Sat, 28 Jan 2012 18:44:48 +0100 Torfinn Ingolfsen wrote: > Hello, > > On Sat, Jan 28, 2012 at 3:03 AM, Conrad J. Sabatier > wrote: > > > I've been thinking for a long time that we need a better way to do > > "make readmes", one that would be properly integrated into our > > ports Mk infrastructure, to take advantage of make's ability to > > recognize which files are up-to-date and which really do need > > rebuilding. > > > > I like to make sure my README.html files are all up-to-date after my > > nightly ports tree update, but with the current scheme, that means > > either rebuilding *all* of the files in the tree, or (as I'm doing > > at present) using some sort of "kludgey" (kludgy?) workaround. > > > > > So people are actually using the readme files? > Are many people using them? > I ask because I *never* use them (unless they are used by 'make > search'?), I always use freshports.org (BTW, thanks for an excellent > service!) when I need to find out anything about a port. > Well, in actual practice, it's true, I don't use them a *lot*, but I do use them from time to time when I'm looking for a new port to install for a certain purpose. It's nice to have up-to-date README.html files locally when the need arises. But they sure are expensive to maintain currently. -- Conrad J. Sabatier conrads@cox.net