title: What's the best way to develop a library using composer?
body: <p>We're starting a new project, and we're managing dependencies with Composer. We'll probably build our app on top of Laravel 4. But we'll also create our own library, which we will use for all our next projects, not just this one.</p>
  
  <p>So, we have this terrible doubt: what's the best way to develop a library using composer?</p>
  
  <p>If we list that new library as a dependency, every time we modify it we will have to commit the change to the repository and then call <code>composer update</code>.</p>
  
  <p>That seems terrible!</p>
  
  <p>Is there a better way to do that?</p>