Check out my first novel, midnight's simulacra!
Subversion: Difference between revisions
From dankwiki
(Created page with 'Really, [http://subversion.tigris.org/ subversion] is no longer where it's at (although it's an excellent replacement for [http://www.nongnu.org/cvs/ cvs], should any unfortunate...') |
No edit summary |
||
| Line 1: | Line 1: | ||
Really, [http://subversion.tigris.org/ subversion] is no longer where it's at (although it's an excellent replacement for [http://www.nongnu.org/cvs/ cvs], should any unfortunate souls still be using that in this day and age). Try distributed source code control systems like [http://git-scm.com/ git]. | Really, [http://subversion.tigris.org/ subversion] is no longer where it's at (although it's an excellent replacement for [http://www.nongnu.org/cvs/ cvs], should any unfortunate souls still be using that in this day and age). Try distributed source code control systems like [http://git-scm.com/ git]. | ||
==Using subversion with build processes== | |||
* Realize that most subversion software, including <tt>svnversion</tt> and <tt>svn-clean</tt>, rely on the <tt>.svn</tt> metadata embedded in checkouts to operate properly. Bundling up this metadata will, generally, roughly double the size of distributed tarballs (especially for repositories with much binary data). | |||
==Keeping $HOME in subversion== | ==Keeping $HOME in subversion== | ||
* ''Don't'' keep transient files under control, particularly things like browser cache or [[bash]] history. | * ''Don't'' keep transient files under control, particularly things like browser cache or [[bash]] history. | ||
* ''Don't'' keep things like [[OpenSSH|ssh]] and [http://www.gnupg.org/ GnuPG] keys in there; use symbolic links and a second repository | * ''Don't'' keep things like [[OpenSSH|ssh]] and [http://www.gnupg.org/ GnuPG] keys in there; use symbolic links and a second repository | ||
Revision as of 01:29, 25 June 2009
Really, subversion is no longer where it's at (although it's an excellent replacement for cvs, should any unfortunate souls still be using that in this day and age). Try distributed source code control systems like git.
Using subversion with build processes
- Realize that most subversion software, including svnversion and svn-clean, rely on the .svn metadata embedded in checkouts to operate properly. Bundling up this metadata will, generally, roughly double the size of distributed tarballs (especially for repositories with much binary data).
