Consider splitting out reccaster EPICS module into its own repository, and include it as a submodule

[jwlodek]

It would be nice if the reccaster EPICS module was a separate repository structured like most of the other module repositories on github to make it easier to automate it's clone/build into IOC applications. It can still be referenced in this repository via a git submodule perhaps?

[jacomago]

Can you not use a sparce checkout https://stackoverflow.com/questions/600079/how-do-i-clone-a-subdirectory-only-of-a-git-repository ?

[jwlodek]

This is basically what I am doing now, but I'd rather not, since it means I have to maintain one off behavior just for this module only. Every other module is just a clone and then a checkout to the right version.

[mdavidsaver]

Maybe a compromise would be to "promote" the contents of client/ to the root, leaving server/ as is?

Of course, a change like this would be disruptive to everyone who already has make -C client. Ah, legacy...

[anderslindho]

I agree fully with this, to separate the two projects (but I would not include as submodule or in any other way). Any particular reason why they have been joined @mdavidsaver @jacomago @shroffk?