Possible Solution to bundling ruby-debug19

In a previous article I posted a solution to ruby-debug19 not building when using rvm. Many people have found this helpful and I’d like to make it a little easier.

The solution I’ve found goes something like this

bundle config build.ruby-debug19 --with-ruby-include=<path to used ruby>

Now this should allow you to just run bundle install with no code puke but I don’t think I like it. I feel that doing this may be encroaching a bit on your team members development environment. In theory we should be using very similar development environments but in practice that doesn’t seem to be the case.

What do you think?

*** UPDATE 2 ***

You should probably just completely disregard this article for now, it must have been a fluke that it worked for me originally. I can no longer reproduce a successful result. Sorry for any misdirection.

*** UPDATE ***

This adds an entry to bundler config located in your $HOME directory. So if you’re using rvm, this may not be the greatest solution… depending on your environment. Still tell me what you think.

Tidly Bits of Knowledge, Shared by You

All right people, I’m going to share a little secret with you. Go ahead come a little closer so you can hear me, this is important. This may be somewhat of a shock to some of you but you’re smart. Yeah I said it, now deal with it. Oh, don’t give me the rolley eye. I know that you’re significant other along with your mother has been telling this to you for years. Go ahead and call them up now to thank them, they were right. (It’s ok, I can wait)

You back? Good.

To start off I’d like to reference a previous article from a while back. Don’t worry, I’m getting to the point. The beginning of this article may have seemed a little hand hold-ey… I’d like to think of it more like a virtual high five. That was all just to pump you up for this tidbit of information.

Like I was saying, you’re smart. If you’re like me you’re probably thinking that you’re not as smart as your peers or have as much to offer. This is not a bad thing… at least not for me. It’s what constantly drives me to become better. It turns out that you’ve already got the skills to offer your peers something.

I feel one of the best things you can do for yourself and your peers/community is to write down the tidbits of knowledge that are most likely trapped in your meat locker. This has been something that I try to keep up with and helps me CONSTANTLY. Also it’s an awesome tool for when you’re mind escapes for a shake break (SHAKE BREAK!). Just go ahead and search for that problem you’re having… Google and your past self probably got your back. Any blog you have will do just fine. I prefer Tumblr just due to me finding it easier to quickly get short form articles out there.

I’ve seen many benefits to this. You know what’s better than searching for a problem solution and finding that you’ve already wrote said solution? Your peers doing that same search and finding your solution. You just helped someone and that feels good. It’s even better when someone tells you they found your solution. Hey and sometimes there is a cherry on top… sometimes it’s someone that you look up to. Which brings us back to my rambling above about confidence.

There is something you know right now that the person doesn’t and quite possibly is having trouble with… RIGHT NOW.

• RIGHT NOW… you’re a smart dude/tte
• RIGHT NOW… someone is in need of knowledge
• RIGHT NOW… that person is next to you
• RIGHT NOW… that person is in another country
• RIGHT NOW… is harder than it looks
• RIGHT NOW… you have the solution

Whoops, how’d Van Halen get in here… I don’t apologize for that.

I do, however, apologize for my rambling thought process. Hopefully I will have motivated you in some way to get tidbits of YOUR knowledge out there. Remember this does not need to be anything long form. I found that as a turn off initially but found that quick problem/solution articles worked for me. As an example, one of my more popular articles is a solution for ruby-debug19/linecache19.