kern/188433: Retiring portsnap
David Noel
david.i.noel at gmail.com
Thu Apr 10 16:40:01 UTC 2014
>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. Its 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:
More information about the freebsd-bugs
mailing list