This version has some minor api differences. So, for instance app-admin/collectd-5.0.0 will fail to build (feels wrong to create a bug about this since yajl-2.0.2 isn't in tree yet?). yajl tests pass for me. Also, i see a *.a file being installed. Hide behind USE="static"? Finally, could this be a candidate for git-2.eclass? Cheers!
I've added yajl-2.0.2 to the tree, thanks for the report. (In reply to comment #0) > This version has some minor api differences. So, for instance > app-admin/collectd-5.0.0 will fail to build (feels wrong to create a bug about > this since yajl-2.0.2 isn't in tree yet?). yajl tests pass for me. I had hoped to install this version into a different slot given the incompatibility, but the package isn't designed for that. My suggestion would be to file a bug with upstream yajl about the breakage and to file on for collectd to work around it. > Also, i see a *.a file being installed. Hide behind USE="static"? Perhaps, but I don't know any cmake so I'm going to pass on that. > Finally, could this be a candidate for git-2.eclass? No, because nothing is done with git on our end. As far as the ebuild is concerned it is just downloading a tarball from a website.
(In reply to comment #1) > I've added yajl-2.0.2 to the tree, thanks for the report. > > (In reply to comment #0) > > This version has some minor api differences. So, for instance > > app-admin/collectd-5.0.0 will fail to build (feels wrong to create a bug about > > this since yajl-2.0.2 isn't in tree yet?). yajl tests pass for me. > > I had hoped to install this version into a different slot given the > incompatibility, but the package isn't designed for that. My suggestion would > be to file a bug with upstream yajl about the breakage and to file on for > collectd to work around it. Our bug is here: bug 374411. I've been in contact with upstream and patch is landed! > > > Also, i see a *.a file being installed. Hide behind USE="static"? > > Perhaps, but I don't know any cmake so I'm going to pass on that. I'll see what I can find; either patch the cmake (and send upstream) or do a find -delete? > > > Finally, could this be a candidate for git-2.eclass? > > No, because nothing is done with git on our end. As far as the ebuild is > concerned it is just downloading a tarball from a website. Good point. My idea was to re-use the solution for ${S} and src_unpack, not much else.
