nodejs July 2014

nodejs@lists.fedoraproject.org

3 participants
3 discussions

Planning for Node.js 0.12.x
by Stephen Gallagher 18 Aug '14

18 Aug '14

-----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/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlO9orQACgkQeiVVYja6o6MAZgCdHjdz6tAAcRDt267IyfhvhDQd WdwAnirQdcA4ZFpHzaiHp+sQ+GHFQ0ar =wr4t -----END PGP SIGNATURE-----

2 2

lodash-node
by Tom Hughes 15 Aug '14

15 Aug '14

I have an existing package that has a new version with a dependency on lodash-node so I was trying to package it but ran into the question of exactly what it is and how to deal with it... We have lodash packaged already and as bast I can figure out lodash-node is the result of using lodash-cli to build node modules from lodash. Though I'm not sure what that means when lodash is already a node module?!? In any case does that mean I should package lodash-cli first and then make the lodash-node package do that build step? Tom -- Tom Hughes (tom(a)compton.nu) http://compton.nu/

3 9

EPEL7 status
by T.C. Hollingsworth 29 Jul '14

29 Jul '14

Unfortunately, I only now just noticed that uglify-js1 was missing from the list of packages to branch. This is deep within the dep chain for nodejs-tap, so a lot of packages are missing the necessary deps to run %check. Please ignore any failed builds for now, I'll finish things up once uglify-js1 is branched. Thanks! -T.C.

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

nodejs July 2014