From owner-freebsd-ports@FreeBSD.ORG  Tue Mar 27 14:35:30 2012
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 2D8B71065670
	for <ports@FreeBSD.org>; Tue, 27 Mar 2012 14:35:30 +0000 (UTC)
	(envelope-from kozlov@ravenloft.kiev.ua)
Received: from ravenloft.kiev.ua (ravenloft.kiev.ua [94.244.131.95])
	by mx1.freebsd.org (Postfix) with ESMTP id DC8708FC1C
	for <ports@FreeBSD.org>; Tue, 27 Mar 2012 14:35:29 +0000 (UTC)
Date: Tue, 27 Mar 2012 17:35:28 +0300
From: Alex Kozlov <spam@rm-rf.kiev.ua>
To: Gerald Pfeifer <gerald@pfeifer.com>, ports@FreeBSD.org
Message-ID: <20120327143528.GA2152@ravenloft.kiev.ua>
References: <alpine.LNX.2.00.1203252051420.4039@gerinyyl.fvgr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LNX.2.00.1203252051420.4039@gerinyyl.fvgr>
Cc: 
Subject: Re: Where are conventions like -devel ports documented?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Mar 2012 14:35:30 -0000

On Sun, Mar 25, 2012 at 11:24:59PM +0300, Gerald Pfeifer wrote:
> Perhaps I am missing the obvious and will be rewarded with
> embarrassement, but where are conventions like the use and
> naming of -devel ports described?
> 
> I would have expected this to be covered in
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html
> but -- it is not.
> 
> (If this is an omission, can someone more closely involved than
> I have been so far donate a paragraph or two?)
> 
> Gerald
> 
> PS: I am thinking to split the existing emulators/wine port into
> two, the regular one (tracking releases of Wine) and a -devel port
> that tracks the bi-weekly snapshots that will lead to the next
> release in a year or two.  Somehow I would prefer something like
> wine-stable / wine instead of wine / wine-devel, but the latter is
> more in line with how we are doing things, right?
In general, $port / $port-devel more common, but in case of wine I think
wine-stable or even wine14 / wine would be better. I suspect that not mouch
people would stick with wine release.


--
Adios