title: Drupal multiple features and unreusable components
body: <p>This is a general question on how Features should be created when we have components that could potentially be used in multiple features.</p>
  
  <p>Suppose a context (c1) takes a view (v1) and is added to a feature (f1).  Now let's say v1 has potential use somewhere else and i want to create a new feature (f2) to include it in...but the Features module doesn't give you the option to do so.  The only thing i can do is cloning v1 into v2 and use that in f2.</p>
  
  <p>I may be shortsighted, but I think that if f2 needed v1, then just add the other components that would make up f2 and put them in f1...because more likely than not, those two features would be closely related (see <a href="http://drupal.org/node/928946" rel="nofollow">One big feature...</a>), at least enough to warrant using the same view (which in turn could include the same node types, roles, etc...)</p>
  
  <p>I guess i'm just curious, has there been a case where you've created a feature with a view, and then needed to have a different feature using that same view?</p>