From owner-freebsd-ports@FreeBSD.ORG Sun May 20 19:28:36 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 1D6011065673; Sun, 20 May 2012 19:28:36 +0000 (UTC) (envelope-from scheidell@FreeBSD.org) Received: from mx2.secnap.com.ionspam.net (mx2.secnap.com.ionspam.net [216.134.223.54]) by mx1.freebsd.org (Postfix) with ESMTP id A42458FC08; Sun, 20 May 2012 19:28:35 +0000 (UTC) Received: from mx2.secnap.com.ionspam.net (unknown [10.71.0.54]) by mx2.secnap.com.ionspam.net (Postfix) with ESMTP id 153E0D23CDA; Sun, 20 May 2012 15:28:35 -0400 (EDT) X-Virus-Scanned: SpammerTrap(r) VPS-1500 2.18 at mx2.secnap.com.ionspam.net Received: from USBCTDC001.secnap.com (unknown [10.70.1.1]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx2.secnap.com.ionspam.net (Postfix) with ESMTPS id 2355CD23C1D; Sun, 20 May 2012 15:28:34 -0400 (EDT) Message-ID: <4FB945E8.1080603@FreeBSD.org> Date: Sun, 20 May 2012 15:28:40 -0400 From: Michael Scheidell Organization: SECNAP Network Security Corp User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.2.20) Gecko/20110804 Thunderbird/3.1.12 MIME-Version: 1.0 To: Chris Rees References: <4FB8E67C.5030001@FreeBSD.org> <4FB90160.9060002@infracaninophile.co.uk> <4FB9437D.5050804@FreeBSD.org> <4FB943B0.6040501@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: PORTVERSION=1.0.0b 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: Sun, 20 May 2012 19:28:36 -0000 On 5/20/12 3:25 PM, Chris Rees wrote: >> any porters handbook, committers habndbook documentation on that? as in why >> > '1.0.0.b' is preferred over '1.0.0b'? > Because as much as possible, we try to standardise things like version > numbers and rc scripts, so people get a more consistent experience, > rather than bowing to the particular upstream/maintainer's view of how > versions work. > so, we need to update committers/porters handbook, or is this some secret thing? another of those 'we won't document it, but we sure as hell will publically lart you if you disobay the unspoken, undocumented secred code ?' or, like I asked 'I need to give a link to submitter to show him this is the best way to do it'. I guess I wait till the email archive is finished and point him to chris's post? -- Michael Scheidell, CTO >*| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell