Dne 23.2.2012 10:17, Tim Serong napsal(a):
So, what's the right course of action? I guess I can patch our version of the gettext gem, assuming we're happy to carry non-upstream patches. Or, I could try to monkey patch around the whole problem in my application, but I don't want to do that, because it's ugly, and it doesn't help anyone else who's going to hit this.
Currently I'm using the monkey patch solution in both SLMS and WebYast. Yes, it would be nice to fix it once and for all. The best solution would be to fix it in gettext gem upstream, but if the maintainers do not care to merge the proposed patches... I'm not sure what's a better solution, our own patched gettext version could save some time to our developers, on the other hand monkey patching has an advantage that it also works with upstream gems (so it works also with bundler or rvm). -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org