I need something akin to submodules, but which exist outside the main repository as a dependency.
Here's the problem:
I'm trying to use Git (in a REALLY awkward way) to manage design files for a CAD tool (Cadsoft Eagle), and I'm having a hard time figuring out if there is a way to use git submodules to manage each project's dependency upon the CAD tool's shared library.
I'm using a folder structure like this:
~/eagle/ <-- Main library used by multiple projects
.git/
<library files>
~/projects/ <-- Projects folder
Proj0/
.git/
<design files>
Proj1/
.git/
<design files>
In this case, it doesn't make sense to add the eagle.git repository as a git submodule for each project.
However, I still need a way to snapshot the current state of the "eagle.git" repository so that if the library is updated in the future, it can be rolled back to access the specific revision of the library files which were being used when the Proj[x] was committed.
Ideally, I'd like something like the following:
~/eagle/ <-- Main library used by multiple projects
.git/
<library files>
~/projects/ <-- Projects folder
Proj0/
.git/
<design files>
**eagle** <-- something that acts like a submodule
but which actually points to ~/eagle/
Proj1/
.git/
<design files>
**eagle** <-- something that acts like a submodule
but which actually points to ~/eagle/
I'd like to be able to:
cd ~/projects/Proj0
git submodule update
and have the ~/eagle/ directory automatically roll back to the revision checked into Proj0.
Anybody know of anything in Git that could allow for this kind of behavior?