search

chrislee35 / passivedns-client

passivedns-client provides a library and a query tool for querying several passive DNS providers
MIT License
198 stars 42 forks source link

LoadError: cannot load such file -- passivedns-client #2

Closed blackfist closed 9 years ago

blackfist commented 10 years ago

Loading the file can be a bit of a challenge. Not sure why. I opened a question at StackOverflow and we were able to come up with a way to load the library. http://stackoverflow.com/questions/26218350/ruby-cannot-load-such-file

Not sure if it is a documentation problem, a user error, or a case of needing more descriptive error messages.

chrislee35 commented 10 years ago

I'm looking into this now. I don't remember why I separated the module out this way, but I'm pretty sure this was recommended to me by another rubyist when I did the refactor after the jeweler gem broke. I did this same pattern in dnsbl-client, snort-rule, and it looks like every other gem that I've built. I'm going to first patch this with updating the README for each gem. Later, I see what new advice is out there for bundling gems. I will probably comment on the stackoverflow thread as well asking for Anthony's (and others) suggestion on how to best architect these gems. Thanks for so much letting me know about this issue! I owe you a frosty beverage.

chrislee35 commented 10 years ago

So, it looks like I got the pathing idea from [1] and if it works for people, I'd like to keep it. There are some good suggestions in [2] that I'd like to use in future projects, but I'm not sure that it's worth renaming and restructuring all my current gems to meet YASS (yet another supposed standard) draft. I'll need time to read through [3], but it looks like a fairly authoritative source for good design. If you have any helpful hints, I need all the pointers that I can get.

[1] http://weblog.rubyonrails.org/2009/9/1/gem-packaging-best-practices/ [2] http://chneukirchen.github.io/rps/ [2] http://guides.rubygems.org/