nodejs-0.11.13-r1.ebuild: =dev-libs/libuv-0.11.25-r1" nodejs-0.11.14.ebuild: =dev-libs/libuv-0.11.25-r1" nodejs-0.11.15.ebuild: =dev-libs/libuv-1.1.0" nodejs-0.12.0.ebuild: =dev-libs/libuv-1.1.0" all of those seem to be too strict you probably want to use the subslots of libuv or even '>=', not specific versions I tested nodejs-0.12.0 with dev-libs/libuv-1.4.2 and it builds and links fine
I would also like to loosen up the requirements on libuv. I have other packages (neovim) requiring the newest version but nodejs is holding it back.
We'll loosen these up the same way we're doing iojs any day now. Thanks for your patience.
Beautiful. Thanks!
What's blocking this? I currently patch every new ebuild to build it with the latest libuv version.
(In reply to Ole Reifschneider from comment #4) > What's blocking this? I currently patch every new ebuild to build it with > the latest libuv version. How are you patching your ebuilds?
(In reply to Ole Reifschneider from comment #4) > What's blocking this? I currently patch every new ebuild to build it with > the latest libuv version. By now it's more than one month, so you can call it maintainer timeout and fix it yourself.
(In reply to Julian Ospald (hasufell) from comment #6) > (In reply to Ole Reifschneider from comment #4) > > What's blocking this? I currently patch every new ebuild to build it with > > the latest libuv version. > > By now it's more than one month, so you can call it maintainer timeout and > fix it yourself. Sorry, I have a work in progress ebuild that fixes all open bugs, but I'll post one that addresses specific issues instead.
Fix (with other things) here: https://github.com/gentoo/gentoo-portage-rsync-mirror/pull/118 Thanks for the nudge, all. Sometimes that's what you need :) Also, thank you for your patience.
This should be fixed since 0.12.2-r2.