Bug 188433 - Retiring portsnap
Summary: Retiring portsnap
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 1.0-CURRENT
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-10 17:40 UTC by David
Modified: 2014-04-14 00:39 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David 2014-04-10 17:40:00 UTC
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.

Fix: 

Remove portsnap from base. Retire the portsnap servers or use them for something else.
Comment 1 jonathan 2014-04-11 08:34:34 UTC
It's all very well having svnlite in 10, but 8 and 9 are still
supported, albeit as legacy options. People running 8 or 9 will still
need the portsnap servers.
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2014-04-14 00:37:33 UTC
State Changed
From-To: open->closed

portsnap is still needed for pre-10.0 systems. 


Comment 3 Mark Linimon freebsd_committer freebsd_triage 2014-04-14 00:37:33 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-bugs