usersfetchingsource

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
usersfetchingsource [2015/08/06 20:09] – PeterWemmusersfetchingsource [2018/06/09 03:38] (current) – historical page MarkLinimon
Line 1: Line 1:
 Page created: 2013-01-27 Page created: 2013-01-27
  
-This page is being linked to by various *BSD news sources and user groups, (Patrick McEvoy et. al.), we'll try to keep this page up to date with the current state of this issue.  Eventually, I hope this page exists merely to announce it's own deprecation- once there is a resolution accepted the %%FreeBSD%% community at large.+This page is being linked to by various *BSD news sources and user groups, (Patrick %%McEvoy%% et. al.), we'll try to keep this page up to date with the current state of this issue.  Eventually, I hope this page exists merely to announce it's own deprecation- once there is a resolution accepted the %%FreeBSD%% community at large.
  
 ==== UPDATE 2 : 2015-08-06 ==== ==== UPDATE 2 : 2015-08-06 ====
Line 7: Line 7:
 Most of the contents of this page are seriously out of date. Most of the contents of this page are seriously out of date.
  
-There is now an in-base version of svn, as /usr/bin/svnlite. This is a stripped down but fully functional client but has the bulky API / language bindings removed.  It has a very lightweight footprint and no external dependencies.  svnlite will make use of the ca_root_nss package in order to validate https certificates, if it is present.+There is now an in-base version of svn, as /usr/bin/svnlite. This is a stripped down but fully functional client but has the bulky API / language bindings removed.  It has a relatively lightweight footprint and no external dependencies.  svnlite will make use of the ca_root_nss package in order to validate https certificates, if it is present.
  
-A packages version can be obtained via:+If you do not have svnlite, or prefer to use the official packaged version, it can be securely obtained:
  
 <code> <code>
Line 22: Line 22:
 </code> </code>
  
-You should use https://svn.freebsd.org/ where practical and so long as ca_root_nss is installed and up to date, the certificate should be automatically validated.+You should use https://svn.freebsd.org/ where practical and so long as ca_root_nss is installed and up to date, the certificate should be automatically checked and securely verified.
  
 svn.freebsd.org connects you to the closest project-operated mirror.  The old legacy mirror names should not be used. svn.freebsd.org connects you to the closest project-operated mirror.  The old legacy mirror names should not be used.
Line 31: Line 31:
   * cvs and cvsup is fully removed and should be ignored.   * cvs and cvsup is fully removed and should be ignored.
   * ctm is obsolete and is thought to be dangerous. Its use should be discouraged.   * ctm is obsolete and is thought to be dangerous. Its use should be discouraged.
-  * svnup can use https to access svn.freebsd.org, but needs the ca_root_nss package. +  * svnup can now use https to access svn.freebsd.org, but it needs the ca_root_nss package. 
-  * Any references to 'pkg_add -r' should be replaced with 'pkg add'+  * Any remaining references to 'pkg_add -r' should be replaced with 'pkg add'.
   * svnup is not expected to be added to base but will remain in ports/packages.   * svnup is not expected to be added to base but will remain in ports/packages.
   * ctm is expected to be removed from base and moved to ports/packages.   * ctm is expected to be removed from base and moved to ports/packages.
Line 46: Line 46:
  
 <code> <code>
-# cd /usr/ports/net/svnup && make install+# pkg install svnup
 # svnup stable -h svn.freebsd.org # svnup stable -h svn.freebsd.org
 </code> </code>
Line 52: Line 52:
 Currently it's a port- but it's such a small binary, it's absolutely a perfect candidate to replace csup(1) in base!  Please note, however, that this port does not yet support fetching over a secure channel (i.e. https), and therefore should only be used on trusted networks. Currently it's a port- but it's such a small binary, it's absolutely a perfect candidate to replace csup(1) in base!  Please note, however, that this port does not yet support fetching over a secure channel (i.e. https), and therefore should only be used on trusted networks.
  
-=== Legacy cvsup Status, (updated 2013-03-10): ===+=== Legacy cvsup Status, (updated 2015-05-26): ===
  
-  * source, cvsup access deprecated - **end-of-life date not set** +  * source, ports, cvsup access fully removed.
-  * ports, cvsup access gone **end-of-life Feb 28, 2013**+
  
 ---- ----
Line 62: Line 61:
  
 At the time of this writing, there is no //in-base// solution for fetching canonical RELEASE sources, (to build and maintain production grade systems). At the time of this writing, there is no //in-base// solution for fetching canonical RELEASE sources, (to build and maintain production grade systems).
 +
 +**UPDATE: no longer true; svnlite is in-base**
  
 For %%FreeBSD%% users, (particularly systems administrators and integrators), fetching source has always been easy - via either c[v]sup or CTM.  Until recently, these tools could also be used to fetch the ports collection.  CTM has not been heavily promoted and has not been as widely used as c[v]sup, but has a strong user base. For %%FreeBSD%% users, (particularly systems administrators and integrators), fetching source has always been easy - via either c[v]sup or CTM.  Until recently, these tools could also be used to fetch the ports collection.  CTM has not been heavily promoted and has not been as widely used as c[v]sup, but has a strong user base.
  
-[[https://wiki.freebsd.org/CvsIsDeprecated|CVS has been deprecated in FreeBSD development for several years now]], and all %%FreeBSD%% development has moved to the more modern [[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/svn.html|SVN]].  While [[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/svn.html|SVN]] is a great leap forward for the development process, c[v]sup has been heavily used by server administrators and system integrators for source management - and a replacement has fallen behind as the CVS infrastructure is being phased out.+[[CvsIsDeprecated|CVS has been deprecated in FreeBSD development for several years now]], and all %%FreeBSD%% development has moved to the more modern [[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/svn.html|SVN]].  While [[http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/svn.html|SVN]] is a great leap forward for the development process, c[v]sup has been heavily used by server administrators and system integrators for source management - and a replacement has fallen behind as the CVS infrastructure is being phased out.
  
 ==== Other methods of fetching source ==== ==== Other methods of fetching source ====
Line 73: Line 74:
   - svnup(1) a tiny utility which can pull deltas from SVN servers:   - svnup(1) a tiny utility which can pull deltas from SVN servers:
  
-**UPDATE: An early version is functional, but not yet in base. (2013 02 23)**+**UPDATE: An early version is functional, but not in base. (2013 02 23)**
  
 The work has been added as a port, **net/svnup**. The work has been added as a port, **net/svnup**.
Line 105: Line 106:
  
 === Q. Why is cvsup/CVS deprecated? === === Q. Why is cvsup/CVS deprecated? ===
-  - The %%FreeBSD%% project has been migrating development from CVS to SVN, since 2008.  Active development using the CVS repositories is over, and cvs service is currently becoming extra management overhead.  It needs to go, calmly.  The requirement to support the CVS exporter prevents use of some SVN functionality.+  - The %%FreeBSD%% project has been migrating development from CVS to SVN, since 2008.  The CVS repository no longer exists.
  
 === Q. Why is installing SVN such a big deal for some users? === === Q. Why is installing SVN such a big deal for some users? ===
Line 263: Line 264:
 Kent S. Gordon, 1997 Kent S. Gordon, 1997
 http://www.mavetju.org/mail/view_message.php?list=freebsd-current&id=209027 http://www.mavetju.org/mail/view_message.php?list=freebsd-current&id=209027
 +
 +----
 +
 +{{tag>Historical}}
  
  • usersfetchingsource.1438891748.txt.gz
  • Last modified: 2015/08/06 20:09
  • by PeterWemm