I have a library and several small programs that use it: how should I structure my git repositories?

Posted by Dan on Programmers See other posts from Programmers or by Dan
Published on 2012-10-09T21:16:30Z Indexed on 2012/10/10 3:52 UTC
Read the original article Hit count: 176

Filed under:

I have some code that uses a library that I and others frequently modify (usually only by adding functions and methods). We each keep a local fork of the library for our own use.

I also have a lot of small "driver" programs (~100 lines) that use the library and are used exclusively by me. Currently, I have both the driver programs and the library in the same repository, because I frequently make changes to both that are logically connected (adding a function to the library and then calling it).

I'd like to merge my fork of the library with my co-workers' forks, but I don't want the driver programs to be part of the merged library.

What's the best way to organize the git repositories for a large, shared library that needs to be merged frequently and a number of small programs that have changes that are connected to changes in the library?

© Programmers or respective owner

Related posts about version-control

Related posts about git