dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.1.0
v1n has joined #cinch
xeviox is now known as xeviox|afk
v1n has quit [Ping timeout: 252 seconds]
v1n has joined #cinch
v1n has quit [Ping timeout: 252 seconds]
nOgAnOo has joined #cinch
nOgAnOo is now known as n0g
n0g is now known as nOgAnOo
masso has joined #cinch
<masso> He guys, I have a little problem with cinch...
<leftylink> I think the only appropriate response to this is "I got 99 problems but a cinch ain't one"
<masso> hm ya, maybe I'm stupid, but somehow it gives me a load error all the time
<masso> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- bundler/setup (LoadError)
<leftylink> I don't think this is cinch's problem, but we can talk about bundler nevertheless
<leftylink> not that I know too much about that anyway, since I only just learned about it at work
<leftylink> ... I guess the obvious question is, "is bundler installed?"
<leftylink> because if not, well, I would understand why there are problems loading it.
<masso> yup
<masso> yeah, then it would be obvious, but it's installed. I tried to run this simple reggie bot, but meh...
<leftylink> and so, if you run some other ruby script that requires bundler/setup, it works, but it doesn't work for this particular bot?
<leftylink> hmmmmmmmmm
<leftylink> hmm, I wonder why that bot requires bundler anyway
<masso> hm, this I don't know...
<masso> re-installing bundler atm (for the second time)
<masso> /var/lib/gems/1.9.1/gems/configru-3.1.0/lib/configru.rb:86:in `block in load_group': server: option required (Configru::OptionRequiredError)
<masso> from /var/lib/gems/1.9.1/gems/configru-3.1.0/lib/configru.rb:65:in `load_group'
<masso> from /var/lib/gems/1.9.1/gems/configru-3.1.0/lib/configru.rb:56:in `reload'
<masso> from /var/lib/gems/1.9.1/gems/configru-3.1.0/lib/configru.rb:65:in `each'
<masso> from /var/lib/gems/1.9.1/gems/configru-3.1.0/lib/configru.rb:40:in `load'
<masso> from reggie.rb:6:in `<main>'
<masso> at least a diffeerent error now :(
<leftylink> what I think this means is that
<leftylink> you need to provide a server
<leftylink> since, you know, it's required
<leftylink> to be fair, the bot you're using doesn't exactly tell you anything about what command line options are required
<leftylink> so that's fun
<masso> ya, that's right, but what I don't understand is
<masso> Fetching gem metadata from http://rubygems.org/..
<masso> Installing cinch (1.1.3)
<masso> Your bundle is complete!
<masso> Installing configru (3.1.0)
<masso> Using bundler (1.3.5)
<masso> why 1.1.3?
<leftylink> I guess the bundle specifies that it wants 1.1.3
<leftylink> which is... kinda funny I guess
<leftylink> see the Gemfile
<masso> yeah, says 1.1.3
<masso> tbh, I don't even understand why there is a Gemfile and a Gemfile.lock
<masso> or better, why are they different?
<masso> Gemfile says: source :rubygems
<masso> Gemfilelock: remote: https://rubygems.org/
<leftylink> this I don't know
<leftylink> at work where we use bundler both Gemfile and Gemfile.lock go in the repo too, and I wasn't sure of the difference between the two
<leftylink> I'm going to read http://stackoverflow.com/questions/7517524 and http://stackoverflow.com/questions/6927442 to figure what this stuff is al about
<masso> as far as I can say atm it's not even about the bot...
<masso> the simple 'hello world' bot doesn't work neither
<masso> well, I guess I give up on that... I read almost everything about it and tested a lot, but nope
<masso> the documentation is not the best at all I'd say
<masso> read 5 things, have like 10 completely different solutions, none of wich is working :(
hephaestus_rg has quit [Quit: hephaestus_rg]
hephaestus_rg has joined #cinch
v1n has joined #cinch
v1n has quit [Ping timeout: 252 seconds]
hephaestus_rg has quit [Quit: hephaestus_rg]
kludge` has quit [Ping timeout: 252 seconds]
kludge` has joined #cinch
masso has quit [Read error: Connection reset by peer]
Zackio has quit [Quit: ZNC - http://znc.in]
Zackio has joined #cinch
Zackio has quit [Read error: Operation timed out]
Zackio has joined #cinch
v1n has joined #cinch
Dwarf has quit [Ping timeout: 244 seconds]
cloud|nix has joined #cinch
cloud|nix has quit [Ping timeout: 264 seconds]
zipper has joined #cinch
<zipper> Uh I want to add a plugin for wolfram alpha support. I have already forked cinch and am wondering whether to add it to the development branch or in the master branch.
<dominikh> neither. the plugins that come with Cinch are example plugins, and they're mostly frozen
<zipper> dominikh: So no need to add a pull request you guys?
<dominikh> that is, we don't just add plugins because they might be useful to someone; all plugins in the examples are there to demonstrate different core features
<dominikh> zipper: nope. I'd recommend making a gem out of the plugin and publishing that instead :)
<dominikh> like people have here en masse: http://rubygems.org/search?query=cinch-
<zipper> It's just one file.
<dominikh> many plugins are
<zipper> wow ok I guess it will be a gem then. I have never made a gem before.
<zipper> Hope it won't be tons of work.
<dominikh> see, about time :) all plugins on https://github.com/orgs/cinchrb/ are also valid gems
<dominikh> so you can see the structure etc
<dominikh> it basically comes down to the correct folder structure, the correct namespace, and a simple gemspec
<zipper> Thank you. I will look at what it takes to write a gem.
<dominikh> if there are any questions, feel free to ask
<zipper> I will.
cloud|nix has joined #cinch
cloud|nix has quit [Ping timeout: 264 seconds]
zipper has quit [Ping timeout: 264 seconds]
Dwarf has joined #cinch
hephaestus_rg has joined #cinch