Unable to Patch C extension gems - What approach?

[Shawn]

Sorry for top posting, I'm unable to quote from this email client. The patch is actually in this thread :-)

This rubygem is actually rubygem-idn the one in fc17 that's emailing me due to broken dependencies. If you are on IRC we can discuss options?

From: "Vít Ondruch" <vondruch at redhat.com>
To: "ruby-sig at lists.fedoraproject.org" <ruby-sig at lists.fedoraproject.org>
Sent: February 9, 2012 3:05 AM
Subject: Re: Unable to Patch C extension gems - What approach?

Dne 9.2.2012 02:14, Shawn Starr napsal(a):
>> This is a problem that Vit has been trying to solve some time ago, here is
>> the discussion with suggested steps (not optimal, but there is probably no
>> better way, yet) [1].
> This is going be a problem. Do we have any official approach? I would rather
> not repackage the gem manually, this is a serious problem for me right now.

Actually you are the first lucky one who needs this. After rebuilding 
most of the packages we really did not meet other gem which needs this 
treatment. There will be no other/better way then the one described in 
link posted by bkabrda.

However, as we need some good example how to do it for guidelines and 
FPC, I'll take a look at this case. Do you have already patch which 
fixes the gem? Are you doing to use this one [1]?

Vit



[1] https://github.com/mihu/idn

_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig