Pretend that the letters are direct git dependencies.
So B = { git = "https://github.com/jordan4ibanez/B" } etc.
If you have:
library B which points to program D.
library C which points to program D.
When you have program A which depends on: B, C, D. And they're all pointing to the same version of the same modules, fpm isn't smart enough to realize that D is already included, so B and C can just import from the import that A does and use that code because it's the same thing.
Expected Behaviour
I expect to be able to chain my imports in a structure that would be allowed in a monolithic program.
Version of fpm
0.10.1, alpha
Platform and Architecture
Linux Mint X86_64
Additional Information
A solution would simply to use a DAG (directed acyclic graph) as one of my friend's recommended to me to use for my own game "mods".
Description
Pretend that the letters are direct git dependencies. So
B = { git = "https://github.com/jordan4ibanez/B" }
etc.If you have: library B which points to program D. library C which points to program D.
When you have program A which depends on: B, C, D. And they're all pointing to the same version of the same modules, fpm isn't smart enough to realize that D is already included, so B and C can just import from the import that A does and use that code because it's the same thing.
Expected Behaviour
I expect to be able to chain my imports in a structure that would be allowed in a monolithic program.
Version of fpm
0.10.1, alpha
Platform and Architecture
Linux Mint X86_64
Additional Information
A solution would simply to use a DAG (directed acyclic graph) as one of my friend's recommended to me to use for my own game "mods".