From owner-freebsd-doc@FreeBSD.ORG Mon Aug 9 17:08:31 2004 Return-Path: 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 86AD316A4CE for ; Mon, 9 Aug 2004 17:08:31 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CB3743D41 for ; Mon, 9 Aug 2004 17:08:29 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])i79H8PfM007441; Mon, 9 Aug 2004 20:08:27 +0300 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) i79H8N1B046107; Mon, 9 Aug 2004 20:08:23 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost)i79H8Naf046106; Mon, 9 Aug 2004 20:08:23 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 9 Aug 2004 20:08:23 +0300 From: Giorgos Keramidas To: Peter Pentchev Message-ID: <20040809170823.GA29688@orion.daedalusnetworks.priv> References: <200408091240.i79CeRw5097120@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408091240.i79CeRw5097120@freefall.freebsd.org> cc: freebsd-doc@freebsd.org Subject: Re: docs/66775: Clarification that port names should not contain version numbers X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Aug 2004 17:08:31 -0000 On 2004-08-09 12:40, Peter Pentchev wrote: > On Sat, Jul 31, 2004 at 09:00:45PM +0000, Aasmund Eikli wrote: > > > > Upgrade the copied port to the new version (remember > > to change the PORTNAME so there > > - are not duplicate ports with the same name). > > + are not duplicate ports with the same name). > > + Alternatively, change LATEST_LINK > > + depending on the purpose. > > > > I think that 'remmeber to change the PORTNAME' and 'change LATEST_LINK' > clauses should be at the same level of "nesting" [...] > How about something like this instead? > > - Upgrade the copied port to the new version (remember > - to change the PORTNAME so there > - are not duplicate ports with the same name). > + Upgrade the copied port to the new version. Remember > + to change either the PORTNAME or > + the LATEST_LINK variable so there > + are not duplicate ports with the same name. Yep, this looks nice. If Aasmund doesn't have any objections or did not mean something different that I misunderstood, this is great. > > p5-Data-Dumper. If the software in question > > has numbers, hyphens, or underscores in its name, you may include > > - them as well (like kinput2). > > + them as well (like kinput2). > > + Make sure that the PORTNAME variable and the > > + PORTVERSION variable contains the name > > ITYM 'contain' here, since both variables form the sentence subject :) > > > + version number of the port respectively. You should not mix > > the two. > > A minor point, but I've gathered the impression that two spaces are > preferred before the start of a new sentence. How about this? Double vs. single space after punctuation is AFAIK a very common cause of many a religious war and lots of flames. "French spacing" with a single space character is preferred by those who either live in French speaking parts of the world or regularly use programs that are smart enough to present nicely typeset and/or copies of the documents they work on. My preference is for double spaces between sentences, but it's not too important; not important enough to force one of the two styles on others, anyway. In short, whatever suits your taste when you commit the text is fine but it would also be awesome if we (all the committers that have access to the doc/ tree) avoided committing stuff just to "fix" French spacing or to revert previous "fixes". > Data::Dumper module becomes > p5-Data-Dumper. If the software in question > has numbers, hyphens, or underscores in its name, you may include > - them as well (like kinput2). > + them as well (like kinput2). Make sure that > + the PORTNAME and > + PORTVERSION variables contain the name and > + the version of the port respectively. You should not mix the > + two. This is great, IMHO. > Thanks for your work on this :) Indeed. Thank you Aasmund!