RT 3.6.0 port

[Erwin Lansing]

On Fri, Jun 23, 2006 at 05:04:36PM -0400, Vivek Khera wrote:
> 
> Also, I've requested a repo copy of rt34 into rt36 for historical  
> purposes, but I'm not sure that's really necessary.  It seems to me  
> we could just make a new port from scratch.  Any opinions on that?
> 
If a new port shared the history of an existing port, usually by being a
newer or development version of a stable port, we do a repocopy for
starting the new port to preserve that history. Without looking at the
patch, I'd say that this rule goes for the rt34 to rt36 move as well.
Unless the new source is completely unrelated to the old one, a repocopy
is the way to go.

Cheers,
-erwin

-- 
Erwin Lansing                                     http://droso.org
Security is like an onion.          (o_ _o)
It's made up of several layers   \\\_\   /_///    erwin at FreeBSD.org
And it makes you cry.            <____) (____>    erwin at aauug.dk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20060623/aed82969/attachment.pgp