You're right - svn update does not work on an export. If you want to stay in sync with the source then you'll need to do a checkout (co) so you use the svn update command.
And if you're using your own code repository to manage your build, then you might want to investigate the svn:externals flags as well - they allow you to have a reference to an external svn project, but not require that you check the entire thing into your repository. http://svnbook.red-bean.com/en/1.0/ch07s03.html http://szeryf.wordpress.com/2007/07/24/rails-plugins-svnexternals/ - scroll down to the "...or another" heading. HTH. H. On 11/9/2008, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: >What is the best way to add extensions managed with svn to a project, co >or export? I am about to pull in Chris's SNS extension and would like to >set it up so that I can stay in sync with his changes. AFAIK, svn update >doesn't work on an export. I could be wrong, I am no svn expert. > > > >~Nate > >_______________________________________________ >Radiant mailing list >Post: Radiant@radiantcms.org >Search: http://radiantcms.org/mailing-list/search/ >Site: http://lists.radiantcms.org/mailman/listinfo/radiant _______________________________________________ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant