http://colin.mollenhour.com/2009/10/17/module-manager-for-when-svnexternals-just-doesnt-cut-it/ Just another WordPress weblog Wed, 18 Aug 2010 18:42:23 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://colin.mollenhour.com/2009/10/17/module-manager-for-when-svnexternals-just-doesnt-cut-it/comment-page-1/#comment-56 Colin Mollenhour’s Technical Blog » Module Manager Update, now on Google Code! Sun, 31 Jan 2010 04:15:42 +0000 http://colin.mollenhour.com/?p=96#comment-56 [...] recently updated Module Manager (first post) to support nested modules and renamed the .modman definitions file to simply modman for easier [...] [...] recently updated Module Manager (first post) to support nested modules and renamed the .modman definitions file to simply modman for easier [...]

]]> http://colin.mollenhour.com/2009/10/17/module-manager-for-when-svnexternals-just-doesnt-cut-it/comment-page-1/#comment-47 colin Thu, 07 Jan 2010 23:00:47 +0000 http://colin.mollenhour.com/?p=96#comment-47 That is great, but the purpose of externals in this case is to separate your code from core code. With svn:externals you would have to mirror the Magento directory structure in your repository which would mean using more than one repository in your installation would most likely not work (can't have two subdirectories checked out in one subdirectory), and you would either have to use svn:ignore *extremely heavily* or your svn status output would be ridiculous (not to mention, slow). The use of softlinks allows you to version only the code that is yours, organize it cleanly, edit it without wading through thousands of core files, and keep svn commands quick. Since intermediate directories are created automatically but not versioned (unlike with svn:externals with files) there is no problem when using multiple modules from different repositories. That is great, but the purpose of externals in this case is to separate your code from core code. With svn:externals you would have to mirror the Magento directory structure in your repository which would mean using more than one repository in your installation would most likely not work (can’t have two subdirectories checked out in one subdirectory), and you would either have to use svn:ignore *extremely heavily* or your svn status output would be ridiculous (not to mention, slow). The use of softlinks allows you to version only the code that is yours, organize it cleanly, edit it without wading through thousands of core files, and keep svn commands quick. Since intermediate directories are created automatically but not versioned (unlike with svn:externals with files) there is no problem when using multiple modules from different repositories.

]]> http://colin.mollenhour.com/2009/10/17/module-manager-for-when-svnexternals-just-doesnt-cut-it/comment-page-1/#comment-46 melicerte Wed, 06 Jan 2010 13:48:47 +0000 http://colin.mollenhour.com/?p=96#comment-46 Subversion 1.6 support svn:externals on a single file. Subversion 1.6 support svn:externals on a single file.

]]>