Best practice for cross-repo dependencies

Viewed 2052

Here is a scenario:

  • Repo A is a monster code with a lot of modules and dependencies. It is not easy to install. It is maintained by someone else and hosted on Github.
  • Repo A contains a module X which is very useful and has almost no dependencies to the rest of Repo A
  • I am maintaining Repo B (hosted on Github), which is small and I hope to make it easy to distribute.
  • I would like to use the functionality of module X in Repo B.

Now I can copy module X into Repo B to achieve this. But if the maintainer of Repo A makes a crucial bug fix to module X, there is no way for me to know that. How do I get around this?

1 Answers
Related