<aspiers>
when bundle fails, it doesn't leave behind a Gemfile.lock so I can't see the dependency tree it was working from
<kgrz>
Use ruby >= 1.9.2, run bundle :)
<kgrz>
@aspiers ^
<aspiers>
kgrz: that really doesn't help. I'm already using 1.9.3 and 2.0.0, but I'm trying to get my tests running on 1.8.7 too which is our target platform
<aspiers>
and believe it or not, there are perfectly good reasons for targeting 1.8.7
<kgrz>
No, I meant, check the Gemfile.lock output in 1.9.2 and then you can know which gem is loading celluloid
<kgrz>
@aspiers ^
<aspiers>
ahh
<aspiers>
except that's a different dependency tree so it might help but there's no guarantee
<aspiers>
I'll try though
<aspiers>
looks like guard -> listen -> celluloid
<aspiers>
also chefspec >= 3 requires fauxhai which requires Ruby >= 1.9, but bundler fails to figure out that it should use chefspec 2
<aspiers>
I guess bundler needs to use satsolver to resolve its dependencies
hagabaka has quit [Read error: Operation timed out]
<aspiers>
Who: no but some of my colleagues wrote libsatsolver
<Who>
great
<Who>
do they hang out on freenode?
deryl has joined #bundler
<aspiers>
Who: thanks very much for your replies
<aspiers>
Who: not sure but I can find out
<Who>
When I started writing the resolver I didn't know much of CS behind it but then I learned it by reading AI modern approach and then fixed other bottlenecks using profile and fix approach
<Who>
so I would be glad to talk with someone who knows more about these stuff :)
<aspiers>
Who: apparently he is not on IRC :-/
<Who>
ah
<Who>
well he is code is out there
<Who>
and its really readable
<Who>
I will see if he has done something interesting
<aspiers>
you could ask on zypp-devel@opensuse.org maybe
<Who>
which I could use :)
<aspiers>
actually, you should also try the #zypp channel
<Who>
sure
<Who>
so about your latest comment
<Who>
so Bundler does something interesting
<Who>
we don't actually install anything while resolving
<Who>
we resolve things first and then we return a list
<Who>
then we install things one by one
<Who>
while we can still keep the tree information
<Who>
but the gem installation is done by Rubygems
<Who>
so that debug message has to wait till we work on merger with Rubygems
<Who>
Though I shouldn't be too quick to dismiss anything, I am just saying this from top of my head
<Who>
but basically it will be difficult
kgrz has joined #bundler
<Who>
since we're piggybacking on Rubygems for installation
<Who>
we can do something like write the Gemflie.lock.broken like you said on exception
chouhoulis has joined #bundler
kgrz has quit [Ping timeout: 240 seconds]
chouhoulis has quit [Read error: Connection reset by peer]
chouhoulis has joined #bundler
chouhoulis has quit [Ping timeout: 240 seconds]
chouhoulis has joined #bundler
kgrz has joined #bundler
deryl has quit [Ping timeout: 240 seconds]
chouhoulis has quit [Remote host closed the connection]
chouhoulis has joined #bundler
shaileshg has quit [Quit: Connection closed for inactivity]
robbyoconnor has quit [Read error: Operation timed out]
chouhoulis has quit [Remote host closed the connection]
robbyoconnor has quit [Read error: Connection reset by peer]
robbyoconnor has joined #bundler
chouhoulis has quit [Ping timeout: 255 seconds]
Who has quit [Quit: Who]
chouhoulis has joined #bundler
kgrz has joined #bundler
kgrz has quit [Ping timeout: 240 seconds]
x1337807x has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
robbyoconnor has quit [Quit: Konversation terminated!]
samphippen has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
robbyoconnor has joined #bundler
samphippen has joined #bundler
derek_ has joined #bundler
<derek_>
Sass devs advise against using CodeKit as it doesn't run it's Sass/Compass through Bundler. Does CodeKit not manage dependencies properly? I'm confused here.
<derek_>
Also can't really find anyone else talking about this, so I feel like I'm missing something...
<derek_>
(or all the talking happened 2 years ago)