Unnecessary dependence on rubigen version fails install
Closed this issue · 1 comments
cjheath commented
Rubigen version match is currently set to 1.3.3 exactly, and I have (and need, for other things) 1.5.2. When I hacked the gem specifications file to say >=1.3.3, everything worked fine using 1.5.2.
Maybe this should be the default?
lukebayes commented
There was a version of rubigen that was released at one time that didn't work for some reason, rather than digging in and figuring out what was wrong, I just added the concrete version dependency. I'll update the source and this fix will be in the next release.
Thanks!