It would be really nice to have yajl-ruby in Fedora. This gem blocks Vagrant as well as Gitorious ( http://ktdreyer.fedorapeople.org/gitorious/graph.png) and I think GitLab would be affected as well.
The review request has been open for a while: https://bugzilla.redhat.com/show_bug.cgi?id=823351
It seems that we're waiting for upstream to merge https://github.com/brianmario/yajl-ruby/pull/113 ?
Is there anything else I can do to get traction on this?
- Ken
Dne 28.5.2014 02:59, Ken Dreyer napsal(a):
It would be really nice to have yajl-ruby in Fedora. This gem blocks Vagrant as well as Gitorious ( http://ktdreyer.fedorapeople.org/gitorious/graph.png) and I think GitLab would be affected as well.
The review request has been open for a while: https://bugzilla.redhat.com/show_bug.cgi?id=823351
It seems that we're waiting for upstream to merge https://github.com/brianmario/yajl-ruby/pull/113 ?
Is there anything else I can do to get traction on this?
Ask FPC for (hopefully temporary) bundling exception?
Vít
On May 28, 2014, at 3:26 AM, Vít Ondruch vondruch@redhat.com wrote:
Dne 28.5.2014 02:59, Ken Dreyer napsal(a):
It would be really nice to have yajl-ruby in Fedora. This gem blocks Vagrant as well as Gitorious ( http://ktdreyer.fedorapeople.org/gitorious/graph.png) and I think GitLab would be affected as well.
The review request has been open for a while: https://bugzilla.redhat.com/show_bug.cgi?id=823351
It seems that we're waiting for upstream to merge https://github.com/brianmario/yajl-ruby/pull/113 ?
Is there anything else I can do to get traction on this?
Ask FPC for (hopefully temporary) bundling exception?
We (at Chef Software, Inc.) are working on an FFI wrapper around YAJL-C that will be released as a totally separate Gem, without any funny business like forking and bundling libyajl.
Once this is done, it will not only unblock the packaging of Chef in Fedora, but will hopefully be of use to others in the community as well that want to transition away from yajl-ruby, which is kind of abandonware.
- Julian
[ Julian C. Dunn jdunn@aquezada.com * Sorry, I'm ] [ WWW: http://www.aquezada.com/staff/julian * only Web 1.0 ] [ gopher://sdf.org/1/users/keymaker/ * compliant! ] [ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]
Dne 13.6.2014 03:54, Julian C. Dunn napsal(a):
On May 28, 2014, at 3:26 AM, Vít Ondruch vondruch@redhat.com wrote:
Dne 28.5.2014 02:59, Ken Dreyer napsal(a):
It would be really nice to have yajl-ruby in Fedora. This gem blocks Vagrant as well as Gitorious ( http://ktdreyer.fedorapeople.org/gitorious/graph.png) and I think GitLab would be affected as well.
The review request has been open for a while: https://bugzilla.redhat.com/show_bug.cgi?id=823351
It seems that we're waiting for upstream to merge https://github.com/brianmario/yajl-ruby/pull/113 ?
Is there anything else I can do to get traction on this?
Ask FPC for (hopefully temporary) bundling exception?
We (at Chef Software, Inc.) are working on an FFI wrapper around YAJL-C that will be released as a totally separate Gem, without any funny business like forking and bundling libyajl.
Interesting. Just out of curiosity, what will be the name?
https://github.com/brianmario/yajl-ruby/pull/128
Not that I am proposing that you should claim the yaml gem prior the yaml-ruby will be renamed ;)
Vít
Once this is done, it will not only unblock the packaging of Chef in Fedora, but will hopefully be of use to others in the community as well that want to transition away from yajl-ruby, which is kind of abandonware.
- Julian
[ Julian C. Dunn jdunn@aquezada.com * Sorry, I'm ] [ WWW: http://www.aquezada.com/staff/julian * only Web 1.0 ] [ gopher://sdf.org/1/users/keymaker/ * compliant! ] [ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]
ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
On Jun 13, 2014, at 3:39 AM, Vít Ondruch vondruch@redhat.com wrote:
Dne 13.6.2014 03:54, Julian C. Dunn napsal(a):
We (at Chef Software, Inc.) are working on an FFI wrapper around YAJL-C that will be released as a totally separate Gem, without any funny business like forking and bundling libyajl.
Interesting. Just out of curiosity, what will be the name?
https://github.com/brianmario/yajl-ruby/pull/128
Not that I am proposing that you should claim the yaml gem prior the yaml-ruby will be renamed ;)
Heh. It will just be called ffi-yajl.
https://github.com/lamont-granquist/ffi-yajl
- Julian
ruby-sig@lists.fedoraproject.org