19:17 <parkr> Hey guys! I have a gem which has a strong dependency (= 0.0.0) on other gems so they can't be accidentally bumped. the problem is, updating any gem requires we create a new branch in our gh repo for that super-gem, then run back to our app and use that branch to test the new version. This takes a lot of time. Is there any way to "override" the super-gem dependency on a sub-gem for testing purposes? If I try to add the gem to the app Gemfi

19:17 <parkr> le, I get a conflict error.

19:18 <parkr> indirect: any thoughts on overriding gem dependencies of a gem in an app?

19:38 <parkr> ixti: can an env var be used in a gemspec?

19:38 <parkr> to specify a version?

21:30 <ixti> parkr: Gemfile is a ruby script, so you can put anything actually in there

21:31 <parkr> ixti: i did this: https://github.com/github/pages-gem/pull/71

21:34 <ixti> parkr: Not sure how that related to Gemfile :D

21:34 <parkr> gemspec

21:34 <ixti> ahhh

21:34 <parkr> gemspec uses `GitHubPages.gems` to calculate dependencies

21:34 <parkr> :)

21:35 <ixti> yeah, i didn't looked into repo :D

21:35 <ixti> well, you definitely can use that

21:35 <ixti> Although I would stick with multiple Gemfiles :D

21:36 <ixti> but idea of env controlling versions for development sound interesting to me :D

21:38 <parkr> ixti: yeah! upgrading github pages versions via the gem but deploying the app etc etc is annoying.

21:39 <ixti> parkr: why not put this all into gemspec directly btw?

21:39 <parkr> so being able to bump versions directly in the app is superior, then let it trickle down into the github-pages gem later

21:40 <parkr> ixti: we push versions into jekyll metadata

21:40 <parkr> need it programmatically available

21:40 <ixti> but you can request gem's dependencies programmatically :D

21:40 <ixti> although your variant is little bit easier, indeed :D

21:41 <parkr> ixti: Gem::Dependency or something? RubyGems is confusing to me. :)

21:41 <parkr> for this: https://help.github.com/articles/repository-metadata-on-github-pages

21:41 <ixti> ah. right. got it.

21:42 <ixti> re Gem::Dependency don't remember at the moment, but somthing like that, yeah :D

21:43 <parkr> :)

21:44 <parkr> alright, i gotta run. thanks for the reply ixti :)