svn commit: r419600 - in head: . lang/pypy lang/pypy3 lang/pypy3-devel lang/pypy3/files

[Mathieu Arnold]

+--On 4 août 2016 13:45:23 +0200 David Naylor <dbn at freebsd.org> wrote:
| On Thursday, 4 August 2016 13:17:12 you wrote:
|> +--On 4 août 2016 08:43:37 +0000 David Naylor <dbn at FreeBSD.org> wrote:
|> | Author: dbn
|> | Date: Thu Aug  4 08:43:36 2016
|> | New Revision: 419600
|> | URL: https://svnweb.freebsd.org/changeset/ports/419600
|> | 
|> | Log:
|> |   lang/pypy3: update to 5.2.0-alpha1
|> |   
|> |   Changes to lang/pypy3:
|> |    - "Rename" from pypy3-devel (functionaly it is a rename, technically
|> | 
|> | pypy3      is a new port and pypy3-devel is deleted).
|> 
|> Please, remove this and add it again starting with svn copy.
| 
| Could you please help me understand the need for this in this case?  
| 
| I considered a `svn cp` however decided against it for the following
| reasons:
| 
| I understand one should normally `svn cp` for continuity, to show the
| history  of a port and how it has evolved.  However, in this case I think
| it will be  confusing as pypy3 is a complete rewrite (based on the diff
| between  lang/pypy3-devel and lang/pypy3, there is only a single line
| that is the  same!).  
| 
| If anything, it is better to `svn cp lang/pypy lang/pypy3` as lang/pypy3 
| internally is based on lang/pypy, not lang/pypy3-devel.  However, since
| lang/  pypy3 is slave port of lang/pypy I think a `svn cp` is not correct
| here  either.  

Then, please do it as a copy of lang/pypy.

-- 
Mathieu Arnold
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-head/attachments/20160804/6b6952b3/attachment.sig>