github - Using git for plugin development -

similar questions have already been asked, although they're not i'm trying do.

at first thought needed git submodule, set superproject , sub tree merge i'm not sure if of these fit.

i have project (eva), , i'm writing extensions it optional. if pull down copy eva github, wouldn't contain optional plugins fetch them separately , use them.

the optional extensions reside in same directory structure eva. simple far ...

eva  |  --- system/  --- events/    |    --- core_events  --- tests/    |    --- core_tests  extension  |  --- events/    |    --- [extension a]  --- tests/    |    --- [extension tests] 

i wanted add tests extensions tonight, , @ present have them in separate directory outside of local eva git repo. in order run these tests need these extension live in same directory eva, events rely on core system run.

eva  |  --- system/  --- events/    |    --- core_events    --- [extension a]    --- [extension b]  --- tests/    |    --- core_tests    --- [extension tests]    --- [extension b tests] 

i copy eva project files extensions repo directory if modify eva's source, have keep copying changes across.

should continue clumsy set or there more graceful way git can accomodate this?

maybe requirements reverse of other questions. extensions sub project of eva , need pull in updates eva repo around occasionally.

if add extensions repo submodule when clones eva they'll optional plugins too? don't want that.

not sure subtree merge fits either, never have pull extensions project core eva project.

i think best option try change project layout such each extension more self-contained, i.e. resides in it's own directory under say, /extensions.

on framework startup/testrun, scan directory , dynamically load extensions. way not makes easy develop , work git, makes easier various packaging-options, i.e. tarballs. makes easy user see extensions used.

you allow 3d-parties develop "out-of-tree" extensions using vcs of choice.