Open pboling opened 11 years ago
For production usage, I recommend forking, hacking on that and hosting your build artifacts (.gem) on gemfury. FWIW I'll consider this project as a test case for a quick gem I'm working on that automates forking, building and uploading gems called furious
.
@pboling Overall, this project appears to be de-facto abandoned and use ancient, nasty antipatterns, i.e., undeclared, programmatically-inaccessible gem dependencies. Consider forking and converting to gemspec-managed bundler dependencies or looking for alternative solutions on ruby-toolbox.
I cannot use this gem like this:
gem 'alter-ego', :git => 'git://github.com/avdi/alter-ego.git'
To pull in the latest pull requests. I can't even do that if I fork it, without pushing up my own gemspec, which seems silly. I would use the rubyforge git, but if I start with that, and then need to fork where do I go, back to github with a remote non-fork?
Also, I just installed the canonical 1.0.1 from rubygems.org, and it pulled in two dependencies that seem unnecessary, hoe and newgem. Probably still uses the old gemspec syntax that doesn't specify dependencies for development only.