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
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
