[development] Getting SVN to deal with orphaned and new files
andrew at drup.org
Wed Nov 25 05:05:59 UTC 2009
The subversion way of doing this is to maintain two separate trees, one is
the subversion repository and the other is the "vendor drop" (i.e. the
latest version of Drupal core/contrib/whatever), kept in your file system.
Each time you have updated your Drupal files (from cvs or using drush) you
run the script: svn_load_dirs.pl
This will update your svn repository copy from your local drupal files, but
what is important is that it will preserve the correct history in the svn
repository so you can see what the changes are. It manages new files,
orphans, and actually lets you tell it about renamed files.
You can then update your website from the repository. If you need to roll it
back, all the svn goodness is available to you.
On Tue, Nov 24, 2009 at 6:19 PM, Shai Gluskin <shai at content2zero.com> wrote:
> I get modules from d.o. from CVS, then I commit them to my own repository
> with SVN.
> When updating modules I've doing SVN del, CVS co, SVN add instead of simply
> CVS up because of orphaned and new files. SVN freaks out over orphans and
> the new files are just a pain since you need to SVN add for each one.
> But I just installed Drush and I'm so excited about making all this easy.
> So I'm motivated to finally ask for help around this.
> So if you commit CVS versions of contrib to SVN, what is your method for
> dealing with orphans and new files?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development