title: Subversion in combination with composer dependencies
body: <p>I want to manage my project with subversion and the project requires dependencies managed by composer.</p>
  
  <p>What is the best practice doing that?</p>
  
  <p>I can add my composer.json with the required dependencies to my trunk.
  Then I run a composer update in my working copy.
  As far as I know i should exclude the folders created by composer from my trunk because they don't need to be copied into the repos. Is this correct?</p>
  
  <p>If i do another checkout i have to do a composer update again. Is this correct?</p>
  
  <p>And if i do an export i have to do another composer update.</p>
  
  <p>The main question is: Is it possible to handle the composer dependencies like svn:externals? If i do a checkout or a export subversion should download the dependencies by itself. Is that possible? Additional i want to be able to do a composer update later by hand.</p>
  
  <p>Sorry but i am a little bit confused about the integration of composer into a subversion repository. Maybe anyone is able to explain it.</p>