On Wed, Apr 20, 2011 at 10:49 AM, Antonio Terceiro <[email protected]> wrote: > This problem will happen with any upstream packages that do not build > correctly, and is not specific to Ruby of gem2deb. In such cases, we > must help upstream to fix their build system, and not add workarounds to > our tools.
This is reasonable to me, I was just wondering if there was a pattern that we could workaround that could save us work. > Please read the last patch I sent. It is a one-line change, and does not > require renaming the extension at all. I can't imagine a reason why > upstream would reject it. I did, and did some testing around it as well. It works for me. I'm somewhat curious about the original reporters issue where it sounds like the wrong extension may have been chosen(?) In all of my testing the extension simply wasn't found. I've filed the bug upstream with your patch. https://github.com/brianmario/yajl-ruby/issues/56 Bryan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
