Dependency dilemma

[schlonzo]

Hi all,

I have a custom library “MyLib” with all my helpers in it, it has its own git. I want to be able to use “MyLib” in multiple projects, which have their own git. My project references “MyLib”, which references my other libraries. Like anton’s gamma automata prototype for example.

Project [GIT A]
   -MyLib [GIT B]
       -Automata
       -Helpers
       -Etc

Some of my “MyLib” components call automata operations, to move from state to state. I want to have access to the automata data type and its operations within “MyLib”, but I want to separate the automata patch completely from the “MyLib” Git.

I want all my projects to reference the same “MyLib”[GIT B], but every project to have their own automata. Is this possible somehow?

[tonfilm]

@schlonzo

but every project to have their own automata.

this already explains it, you have to put everything that is project-specific into the project repository. so if your lib depends on project-specific implementations, it can only ever work for one project.

so extract the project-specific code, in your case the calls to the automata, and put it into each project. then you can use all general functionality from your lib in all projects.