From owner-freebsd-ports-bugs@FreeBSD.ORG Sun Jun 24 10:50:11 2012 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A4B97106568A for ; Sun, 24 Jun 2012 10:50:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 856588FC14 for ; Sun, 24 Jun 2012 10:50:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5OAoBkb001654 for ; Sun, 24 Jun 2012 10:50:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5OAoBM0001653; Sun, 24 Jun 2012 10:50:11 GMT (envelope-from gnats) Date: Sun, 24 Jun 2012 10:50:11 GMT Message-Id: <201206241050.q5OAoBM0001653@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Michael Scheidell Cc: Subject: Re: ports/168404: [NEW PORT] databases/dev-sqlite3: This is a development SQLite version X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Michael Scheidell List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2012 10:50:11 -0000 The following reply was made to PR ports/168404; it has been noted by GNATS. From: Michael Scheidell To: , Cc: Subject: Re: ports/168404: [NEW PORT] databases/dev-sqlite3: This is a development SQLite version Date: Sun, 24 Jun 2012 06:41:48 -0400 --------------070707010100050109010300 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit This should be accomplished with a REPOCOPY first (to retain history from databases/sqlite3) and, for conventional consistency, should be sqlite3-devel The steps for a repo copy are : (open a new pr, its easier) and old pr's tend to be ignored, so, ask that this one be closed: (you make your own copy manually: rsync -avC databases/sqlite3/ databases/sqllite3-devel/) patch up databases/sqllite3-devel (suffix -devel, not prefix dev-) [REPOCOPY] databases/sqlite3 -> databases/sqlite3-devel attach the patch in the pr. class should be 'repocopy'. someone till take the pr, and set Responsible to portmgr, portmgr will perform the repocopy, and assign it back to committer. committer will grab new port from cvs, and apply patches and commit the 'changes' this way, you preserve cvs history, going from sqlite3-> devel-sqlite3. -- Michael Scheidell, CTO >*| * SECNAP Network Security Corporation d: +1.561.948.2259 w: http://people.freebsd.org/~scheidell --------------070707010100050109010300 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit This should be accomplished with a REPOCOPY first (to retain history from databases/sqlite3)

and, for conventional consistency, should be sqlite3-devel

The steps for a repo copy are :

(open a new pr, its easier) and old pr's tend to be ignored, so, ask that this one be closed:
(you make your own copy manually: rsync -avC databases/sqlite3/ databases/sqllite3-devel/)

patch up databases/sqllite3-devel (suffix -devel, not prefix dev-)

[REPOCOPY] databases/sqlite3 -> databases/sqlite3-devel

attach the patch in the pr.

class should be 'repocopy'.

someone till take the pr, and set Responsible to portmgr, portmgr will perform the repocopy, and assign it back to committer.
committer will grab new port from cvs, and apply patches and commit the 'changes'

this way, you preserve cvs history, going from sqlite3-> devel-sqlite3.

--
Michael Scheidell, CTO
> | SECNAP Network Security Corporation
d: +1.561.948.2259
w: http://people.freebsd.org/~scheidell

--------------070707010100050109010300--