kern/188433: Retiring portsnap

--===============2917459748616487287==
Content-Type: text/plain


>Number:         188433
>Category:       kern
>Synopsis:       Retiring portsnap
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Apr 10 16:40:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator:     David Noel
>Release:        
>Organization:
>Environment:
>Description:
With the inclusion of svnlite in 10 the question comes up of whether we really need the portsnap system or whether it could be safely retired.

The reason I see for it to be retired is that subversion allows us to easily and securely check out the ports tree. It旧 a one-line command: `svn co https://...`. Keeping it up-to-date it is another one-liner: `cd /usr/ports; svn update`. With the inclusion of svnlite in base, the portsnap code and servers acting as mirrors become redundant and seem like a waste of resources.
>How-To-Repeat:

>Fix:
Remove portsnap from base. Retire the portsnap servers or use them for something else.

>Release-Note:
>Audit-Trail:
>Unformatted:

--===============2917459748616487287==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
[e-mail] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[e-mail]"
--===============2917459748616487287==--