Date: Thu, 10 Apr 2014 16:33:45 GMT From: David Noel <david.i.noel@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/188433: Retiring portsnap Message-ID: <201404101633.s3AGXjLj066765@cgiserv.freebsd.org> Resent-Message-ID: <201404101640.s3AGe0Wf044966@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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’s 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:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201404101633.s3AGXjLj066765>