Re: F24 System Wide Change: Node.js 4.2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/02/2015 07:39 AM, Vít Ondruch wrote:
Dne 2.12.2015 v 09:41 Tom Hughes napsal(a):
> On 02/12/15 08:27, Vít Ondruch wrote:
>
>> Is there some testing version of v8 somewhere? Will we have
>> time to play with rubygem-therubyracer, if we can convince it
>> to run with recent v8 or what else have to be done? The same
>> applies for MongoDB if I am not mistaken.
> Stephen Gallagher built nodejs 4.2.2 in the side tag last night,
> but using a bundled v8 so it shouldn't affect other users of v8.
While the scope says:
== Scope == Proposal owners: * Update v8
Thanks, I need to update that. It was expected when I wrote it, but
that has changed. One advantage here is that Fedora can opt to carry
whatever version of v8 makes sense for other consumers.
> The spec file now says:
>
> # Node.js is closely tied to the version of v8 that is used with
> it. It makes # sense to use the bundled version because upstream
> consistently breaks ABI # even in point releases. Node.js
> upstream has now removed the ability to build # against a shared
> system version entirely. # See
> https://github.com/nodejs/node/commit/d726a177ed59c37cf5306983ed00ecd858c...
>
>
Provides: bundled(v8) = 4.6.85
That is sad ... although they do expect this commit might get
reverted ...
It's not my preference, certainly. But I spoke with some of the
upstream developers and the simple truth is that they have been broken
consistently by upstream v8 breaking ABI and even API in point
releases. Until and unless Google decides to treat v8 like a shared
lib instead of the copylib that it really is, the only sensible
approach here is to bundle it.
In accordance with the bundling policy, it *is* carrying a virtual
Provides to allow us to identify whether it is affected by discovered
CVEs.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlZfAGYACgkQeiVVYja6o6NI1ACgpICyaqLpwluXDPd/wFr64FR6
QLMAn1Uuhgk03vNN0tLm5P6T+/WiuxJ+
=O0S/
-----END PGP SIGNATURE-----