[Wiki] changed: ReleaseManagement

mrubinsk  Fri, 16 Jan 2009 15:22:01 -0500

Modified page: http://wiki.horde.org/ReleaseManagement
New Revision:  2.17
Change log:  Blurb about using applications symlinked from git

@@ -86,9 +86,9 @@
  horde-fw-symlinks.php --src /usr/local/horde-hatchery/framework  
--dest /var/www/gitpear
  </code>


-* For the actual Horde applications that have been moved to Git,  
there are a few options.  You could either copy the application  
directory back and forth from your /horde directory, or you could try  
to use a joint CVS/Git source tree.  Both methods have drawbacks.  
Issues with the former are obvious - you need to pull, copy, code,  
copy, push etc... The issue with second method is that you will either  
get lots of warnings about files that aren't tracked, or you could try  
to manage an ignore list for both CVS and Git.
+* For the actual Horde applications that have been moved to Git,  
there are a few options.  You could either copy the application  
directory back and forth from your /horde directory, you could try to  
use a joint CVS/Git source tree, or you can symlink the application  
into your horde/ directory.  Both methods have drawbacks. Issues with  
the first are obvious - you need to pull, copy, code, copy, push  
etc... The issue with second method is that you will either get lots  
of warnings about files that aren't tracked, or you could try to  
manage an ignore list for both CVS and Git. If you use a symlink, you  
will need to create a file base.local.php in the application's lib/  
directory - and define your HORDE_BASE in that file.

  ++ Roadmaps

  +++ Horde


--
To unsubscribe, mail: [email protected]