Bluprint inheritance

[hobbes7878]

Opening for discussion...

One of the main goals of bluprint is to make it easy to spin off small, reusable customizations. So if I have a set of components I like to use in our graphics rig, I can create a Jon's own-brand graphics rig bluprint. Great! But now updates are happening in the main bluprint I spun off from. How do keep my bluprint up-to-date?

Parts might be an answer. If the updates happened in a part of the parent bluprint, I can run it in my child and pick up that update. That might work for me as a once off, but it doesn't scale terribly well, and it assumes you know you need to update, which cuts against the idea of pushing changes to users that's so nice about bluprint.

Seems like a better system would be to register what bluprint a child inherits from, capturing the version of the parent as a dependency. Maybe we even want to always overwrite specific files in the child with ones from a parent.

Maybe the easier way to think about it is ... How would you write the bluprint config to specify that it inherits from another bluprint?

Any thoughts? @MatthewWeberTR @fcage @chriscanipe