15:18 <dcolebatch> Good morning all!

15:19 <dcolebatch> Is there a timeline for the v1.8.0 release? …we want to submit a patch to the s3_fetcher (and corresponding specs) so it works with keys that have special chars in it… URI seems to barf now.

15:37 <dcolebatch> Submitted https://github.com/bundler/bundler/pull/3345 with realistic AWS keys working

17:11 <indirect_> dcolebatch: there isn't a really strong timeline, and I would definitely like to ship 1.8 with your fix

17:23 <dcolebatch> Ok indirect_ thanks for that. We are just testin

17:23 <dcolebatch> * Ok indirect_ thanks for that. We are just testing that patch with a rubygems we also patched (for the remote_fetcher)

17:25 <indirect> dcolebatch: if Rubygems also needs to be patched for it to work in Bundler, please add a version check with a warning to your Bundler patch :) Bundler 1.8 has to work with Rubygems versions 1.3.6+

17:29 <dcolebatch> Yeah, that’s what we’re working. 1.3.6+ eh? Damn, we were only using 2.4.3+

17:32 <dcolebatch> Ok indirect - that won’t be a problem. Thanks, lookout for an update to the PR from pangloss.

17:32 <indirect> dcolebatch: sadly, yeah :/ that’s why it’s a pull blocker to touch Gem.anything

17:32 <indirect> because the Gem API has changed soooo much between 1.3 and 2.4

17:37 <dcolebatch> righto, we thought it was fair game because we saw it in other places

17:37 <dcolebatch> but no biggie. One of the main problems with the s3 support as it is, is that the keys have special chars...

17:38 <dcolebatch> if you could add id: and secret: to the Gemfile DSL, then the whole thing becomes a lot easier.

20:49 <indirect> dcolebatch: you mean like `source “s3://blah”, id: “foo”, secet: “bar”`?

20:49 <indirect> the entire reason we accepted the original pull request was that it was “so easy” and “already part of rubygems” :P

20:50 <indirect> I think the real solution is to have plugins that allow different source types

20:50 <indirect> it’s not really practical to support every possible way to get gems directly inside Bundler

20:50 <indirect> that would mean the S3 source plugin could use whatever arguments you want :P

20:57 <dcolebatch> plugins would be nice, we were looking for a neat way to write plugins when we started...

20:58 <indirect> there isn’t one yet, but we’re working on it

20:59 <dcolebatch> I think our PR is going to die on the vine today though. In looking further, it’s just too much work for us to get bundler to accept s3 sources properly (made worse because the rubygems implementation also doesn’t work). The team is just going back to geminabox for now.

21:26 <postmodern> when using system ruby, will `bundle install` ask for sudo or will it just try to install into the gem root?