{"ref":"refs/heads/no_jeweler","commits":[{"author":{"name":"Tim Harper","email":"0441103e2a9c18cb18635c3ff15461c144dd7f5c@gmail.com"},"url":"https://api.github.com/repos/lmp/soca/commits/f47f9b87f3760f06385370802d82480333b20ea4","message":"Remove Jeweler\n\nGems are just as easy to release without Jeweler than it is with it.  It\nusually gets needlessly injected as a runtime dependency (the gemspec it\ngenerated for soca did mark itself as a development dependency in one of\nthe conditional branches, but in reality, using rubygems 1.8.7 and ruby\n1.9.2, it's getting included as a runtime dependency). Why does this\nmatter?  Jeweler has other dependencies, such as bundler.  Not only such\nas bundler, but bundler 1.0! If you are using bundler 1.1, you get\nneedless dependency headaches.\n\nTrue, this could be fixed upstream in jeweler. But I don't think it's\nworth it since it is so easy (easier?) to build gems without jeweler.\n\nThere was a place for jeweler back when we had servers that built gems\nautomatically. Since now the convention is to build the gem locally and\npush it to the server, we can write as much ruby code as we like in the\ngemspec. The gemspec gets expanded and re-serialized without the code,\nso you can use things like Date.today, etc. (tar xzf the generated gem\nif you don't believe me)","sha":"f47f9b87f3760f06385370802d82480333b20ea4"}],"head":"f47f9b87f3760f06385370802d82480333b20ea4","size":1,"push_id":47835197}