-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I was talking with Igor Gnatenko today about libuv 0.11.x. He has a package (neovim) that requires the newer libuv to operate.
I explained to him that updating libuv to 0.11.x in Fedora would necessitate the chain-reaction of updating Node.js, npm and many if not most of the packages that depend on it.
Igor suggested that we could start doing this in Rawhide now, post-branch. I'm a little bit wary of doing this directly in Rawhide, primarily because Joyent has provided no clear target date for the stable release of 0.12.x (and I'm concerned that if it's not ready in time for Fedora 22 Alpha, we might have a problem). Igor and I have contacted Joyent to ask them if they can put a ballpark date on the release.
In the meantime, I'm going to start putting together a COPR repository[1] containing the unstable bits. I think it's probably a good idea for us to at least start exploring what set of packages will work with the new Node.js and which ones are going to break.
I'm definitely the wrong person to do most of this, so I'd like to ask any subscriber on this list who is interested in helping to respond with their FAS ID so I can add them to the permission list on the COPR. Then they can start performing builds in the COPR.
I will hopefully start with libuv and Node.js 0.11.x this afternoon or tomorrow morning.
[1] http://copr.fedoraproject.org/coprs/sgallagh/nodejs-0.12/
On Wed, Jul 9, 2014 at 1:14 PM, Stephen Gallagher sgallagh@redhat.com wrote:
In the meantime, I'm going to start putting together a COPR repository[1] containing the unstable bits. I think it's probably a good idea for us to at least start exploring what set of packages will work with the new Node.js and which ones are going to break.
I'm definitely the wrong person to do most of this, so I'd like to ask any subscriber on this list who is interested in helping to respond with their FAS ID so I can add them to the permission list on the COPR. Then they can start performing builds in the COPR.
I will hopefully start with libuv and Node.js 0.11.x this afternoon or tomorrow morning.
Thanks for getting this started, Stephen!
I've now found some time to work on this some so I requested permissions in COPR and at should at least have a v8 package ready, if not a node package by the time you get to approving it.
Thanks again, -T.C.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 08/16/2014 12:23 AM, T.C. Hollingsworth wrote:
On Wed, Jul 9, 2014 at 1:14 PM, Stephen Gallagher sgallagh@redhat.com wrote:
In the meantime, I'm going to start putting together a COPR repository[1] containing the unstable bits. I think it's probably a good idea for us to at least start exploring what set of packages will work with the new Node.js and which ones are going to break.
I'm definitely the wrong person to do most of this, so I'd like to ask any subscriber on this list who is interested in helping to respond with their FAS ID so I can add them to the permission list on the COPR. Then they can start performing builds in the COPR.
I will hopefully start with libuv and Node.js 0.11.x this afternoon or tomorrow morning.
Thanks for getting this started, Stephen!
I've now found some time to work on this some so I requested permissions in COPR and at should at least have a v8 package ready, if not a node package by the time you get to approving it.
Permissions granted (and I made you an admin, patches). Sorry it took so long; I've been traveling for work these last two weeks.
nodejs@lists.fedoraproject.org