Date: Sun, 24 Jun 2012 10:50:11 GMT From: Michael Scheidell <scheidell@FreeBSD.org> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/168404: [NEW PORT] databases/dev-sqlite3: This is a development SQLite version Message-ID: <201206241050.q5OAoBM0001653@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/168404; it has been noted by GNATS. From: Michael Scheidell <scheidell@FreeBSD.org> To: <bug-followup@FreeBSD.org>, <pavelivolkov@googlemail.com> 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 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000000" bgcolor="#ffffff"> This should be accomplished with a REPOCOPY first (to retain history from databases/sqlite3)<br> <br> and, for conventional consistency, should be sqlite3-devel<br> <br> The steps for a repo copy are :<br> <br> (open a new pr, its easier) and old pr's tend to be ignored, so, ask that this one be closed:<br> (you make your own copy manually: rsync -avC databases/sqlite3/ databases/sqllite3-devel/)<br> <br> patch up databases/sqllite3-devel (suffix -devel, not prefix dev-)<br> <br> [REPOCOPY] databases/sqlite3 -> databases/sqlite3-devel<br> <br> attach the patch in the pr.<br> <br> class should be 'repocopy'.<br> <br> someone till take the pr, and set Responsible to portmgr, portmgr will perform the repocopy, and assign it back to committer.<br> committer will grab new port from cvs, and apply patches and commit the 'changes'<br> <br> this way, you preserve cvs history, going from sqlite3-> devel-sqlite3.<br> <br> <div class="moz-signature">-- <br> Michael Scheidell, CTO<br> <font color="#999999">></font><font color="#cc0000"> <b>| </b></font> SECNAP Network Security Corporation<br> d: +1.561.948.2259<br> w: <a class="moz-txt-link-freetext" href="http://people.freebsd.org/~scheidell">http://people.freebsd.org/~scheidell</a> </div> </body> </html> --------------070707010100050109010300--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201206241050.q5OAoBM0001653>