I am resolving this same issue in Celluloid. My solution is to combine many
repositories into one omnirepo going forward, but that's because it's a highly
active F/OSS repository set. But the solution I currently use might actually
work for you...

  

Notice how it's injected, per gem:
https://github.com/celluloid/culture/blob/master/SYNC.md

  

https://github.com/celluloid/culture/blob/master/gems/loader.rb  

https://github.com/celluloid/celluloid/blob/master/celluloid.gemspec  

https://github.com/celluloid/celluloid/blob/master/Gemfile  

https://github.com/celluloid/culture/blob/master/gems/dependencies.yml  

  

Hopefully that helps a little in getting around the circular-dependency issue
while giving you a fast workflow for changing all the dependency sets at once.
Sort of a hackish approach, but it's one I've hashed out at length with
Bundler's team in the past, and taken a lot of heat for already elsewhere.
Still, it has held together through several releases.

On Jun 4 2016, at 10:33 pm, Guyren Howe <[email protected]> wrote:  

> I'm developing a fairly large collection of what you might call micro-gems.
I've about a dozen now and more to come.

>

> There doesn't seem to be a way to manage loading these things while I'm in
development that isn't remarkably painful. I can't specify their
interdependencies in the gemspecs, because I can't specify a path in a
gemspec. The only way I can find to make it work is to include the
dependencies in the Gemfiles. But if gems A and B need gem C, I can't just put
C in A's gemfile and expect it to be visible from B. It seems I have to
laboriously provide explicit gem dependency inclusions in every gem.

>

> This is turning into a maintenance nightmare, and will be worse when I want
to release all this because I've got to go through and empty out all the
dependencies in all the Gemfiles first.

>

> What am I missing, or is this in fact just something I have to accept?

>

> \--  
\--  
SD Ruby mailing list  
[email protected]  
<http://groups.google.com/group/sdruby>  
\---  
You received this message because you are subscribed to the Google Groups "SD
Ruby" group.  
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].  
For more options, visit https://groups.google.com/d/optout.

-- 
-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
--- 
You received this message because you are subscribed to the Google Groups "SD 
Ruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to