havenwood has quit [Remote host closed the connection]
DanKnox is now known as DanKnox_away
einarj has joined #rubygems
wycats has joined #rubygems
guilleiguaran_ has joined #rubygems
redmenace has joined #rubygems
havenwood has joined #rubygems
roidrage has joined #rubygems
havenwood has quit [Remote host closed the connection]
havenwood has joined #rubygems
sbeam has joined #rubygems
sbeam has quit [Remote host closed the connection]
havenwood has quit [Remote host closed the connection]
tcopeland1 has quit [Quit: Leaving.]
redmenace has quit [Ping timeout: 272 seconds]
havenwood has joined #rubygems
cowboyd has joined #rubygems
stayarrr has quit [Quit: Leaving...]
havenwood has quit [Remote host closed the connection]
kalleth_ has joined #rubygems
kalleth has quit [Ping timeout: 246 seconds]
cowboyd has quit [Remote host closed the connection]
ezkl has joined #rubygems
rafaelfranca has joined #rubygems
redmenace has joined #rubygems
redmenace has quit [Ping timeout: 265 seconds]
skoodge has joined #rubygems
<skoodge>
I would like to include a C binary as part of a gem in my bin/ directory, but ruby tries to execute this binary file as a ruby script. How can I tell rubygems to treat it as a binary file?
stayarrr has joined #rubygems
rafaelfranca has quit [Remote host closed the connection]
cowboyd has joined #rubygems
huoxito has joined #rubygems
arthurnn has joined #rubygems
jnimety has joined #rubygems
stevenharman has joined #rubygems
ZachBeta has joined #rubygems
jnimety has quit [Quit: Computer has gone to sleep.]
brianwong has left #rubygems [#rubygems]
<dwradcliffe>
shaiguitar: you around?
cowboyd has quit [Remote host closed the connection]
ZachBeta has quit [Quit: Computer has gone to sleep.]
havenwood has joined #rubygems
ZachBeta has joined #rubygems
jnimety has joined #rubygems
stevenharman has quit [Quit: Leaving...]
stevenharman has joined #rubygems
roidrage has quit [Quit: Leaving...]
almostwhitehat has joined #rubygems
csaunders has quit [Remote host closed the connection]
csaunders has joined #rubygems
huoxito has quit [Remote host closed the connection]
huoxito has joined #rubygems
huoxito has quit [Ping timeout: 248 seconds]
sebson has quit [Quit: Leaving]
jnimety has quit [Quit: Computer has gone to sleep.]
<drbrain>
indirect: also, I have gem 'a', path: 'vendor/a' mostly working
<drbrain>
for gem dependencies files
<indirect>
oh nice
<indirect>
fyi I learned about some rubygems resolver bugs in Israel
<drbrain>
did you get them reported?
<indirect>
I asked the maintainer to report them
<indirect>
since I don't have details
<drbrain>
:/
<indirect>
yeah :\
<indirect>
is your intention to support the full Gemfile DSL?
<drbrain>
once I get path: working I can get git: working, through a plugin at worst
<drbrain>
I am unsure how much I want to stand on principles :D
jfoy has joined #rubygems
<drbrain>
do the path: gems get installed anywhere?
<drbrain>
or do they just sit there and get shoved onto $LOAD_PATH?
<drbrain>
and do they work without `bundle exec` or `Bundler.setup`?
<indirect>
haha
<indirect>
they just sit there
<indirect>
get shoved into #LOAD_PATH
<indirect>
and they do not work without bundle exec or bundler setup
<drbrain>
that makes my work significantly easier!
<indirect>
yup
<indirect>
I think it is git that will be harder
<drbrain>
the same is true for git: gems? or not?
<indirect>
git gems check out a full bare repo, and are then cloned at the sha that is in the lockfile
<indirect>
do you support lock files?
<drbrain>
I'm not sure
<indirect>
okay
<drbrain>
I haven't run across it yet
<indirect>
git basically only makes sense if you know the exact sha
* drbrain
nods
<indirect>
(tbh, I'm not totally clear on why we're implementing the same functionality in parallel, but I'm happy to help you if you want to do it!)
<drbrain>
IMO, at this point, RubyGems may as well take over the core functionality of Bundler
<drbrain>
otherwise we're wasting time maintaining the same thing twice
<drbrain>
we also have to keep working around each other's bugs, which is more waste
jfoy has quit [Quit: jfoy]
<drbrain>
heh, I think I found a bug in the RubyGems resolver just now
<indirect>
drbrain: at this point? meaning you guys have some of the functionality already implemented?
<drbrain>
evan added some Gemfile support for 2.0
<drbrain>
didn't support group, path, git, or platform (besides ruby)
<indirect>
yeah
<indirect>
platform is a terrible hack :(
<indirect>
I would love to have cleaner and non-hacky bundler functionality, I'm just not sure how to get there from here
<drbrain>
(besides platform) have me implement it RubyGems, obviously‼
<indirect>
haha
<drbrain>
bundler's platform support is like RubyGems' platform support pre when I improved it back in 0.9.5 or whatever
<drbrain>
probably easier for me to implement what bundler has now, then improve it following that after discussions
<dwradcliffe>
drbrain: thanks for the merge. I already had access I just wanted to let someone else eyeball it :)
<drbrain>
ah, ok
<drbrain>
I figured you already did
<drbrain>
but now you have double access
<dwradcliffe>
drbrain: win!
zachrab has joined #rubygems
zachrab has quit [Remote host closed the connection]
arthurnn has joined #rubygems
arthurnn has quit [Ping timeout: 272 seconds]
<indirect>
drbrain: bundler kind of has two different levels or kinds of platform support, and one is simply honoring rubygems' platforms... the other one is disabling gems except on a certain combo of interpreter and ruby version, because they are incompatible in spite of the rubygems platform claiming they are
<drbrain>
indirect: yeah
<drbrain>
I had so gathered from Gemfile(5)
<drbrain>
in general, I figure I need to support Gemfile stuff in order for you to switch over to the rubygems resolver