You can still have the benefits of relative links without a single repo if you create a dir at the root level.
For example, you can have a /facebook/ dir on every machine with the source, and all your subprojects can assume they are working off that, ie:
include /facebook/somemodule
Re:Scaling Mercurial at Facebook
by markcampbell on Tuesday January 07, 2014 @04:42PM
(#7020169)
There's a solution to this. Git submodules.
Please tell me if there's a way to make git-grep (or git-log for that matter) work between submodules.
While I may not personally like behemoth repositories, I do see why people would choose to endure them. They do have their advantages, even if they all eventually end up looking something like BSD ports. (FYI: I happen to like the extremely modular one-git-repo-per-component approach as used in Mer. Hell, I did an early implementation of the OBS+git -based autobuild system back in 2009!)
Sometimes the cure is worse than the disease.
libs
libs/mylib
apps
apps/myapp
then myapp can reference library mylib via ../../libs/mylib
If all of these things are in separate repositories, all bets are off about how their paths relate to each other on the local filesystem, resulting in more complicated build procedures.