Gentoo Archives: gentoo-dev

From: "Paweł Hajdan
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] does v8 shared library make sense with current upstream approach?
Date: Mon, 23 Sep 2013 00:18:06
Message-Id: 523F88B1.2000003@gentoo.org
1 I'd like to get your feedback and opinion about removing shared v8
2 library package from Gentoo. It's currently used by www-client/chromium,
3 dev-db/drizzle, dev-db/mongodb, dev-lang/v8cgi and sci-geosciences/osgearth.
4
5 net-libs/nodejs switched back to bundled v8 a long time ago:
6
7 25 Feb 2013; Patrick Lauer +nodejs-0.6.21-r2.ebuild,
8 +nodejs-0.8.20.ebuild:
9 Version bump for 0.6 and 0.8 that also disables shared v8 as our v8
10 maintainers remove all compatible versions
11
12 Some bugs for reference:
13
14 https://bugs.gentoo.org/show_bug.cgi?id=417879
15 https://bugs.gentoo.org/show_bug.cgi?id=420995
16 https://bugs.gentoo.org/show_bug.cgi?id=471582
17 https://bugs.gentoo.org/show_bug.cgi?id=477300
18 https://bugs.gentoo.org/show_bug.cgi?id=484786
19
20 From mongodb upstream <https://jira.mongodb.org/browse/SERVER-10282> :
21 "compiling with versions of v8 other than what is included is not
22 currently supported."
23
24 I'd like maintainers of all packages depending on dev-lang/v8 to make
25 their packages use bundled v8 copy instead (I can file bugs for that,
26 let's discuss here whether it should be done).
27
28 For now V8 upstream gives no guarantees about API/ABI stability and
29 actually breaks it very often
30 (<http://upstream-tracker.org/versions/v8.html>). Having a shared
31 library so closely tied to packages (which results in frustrating
32 blockers, since v8 is updated often and chromium is synchronized with
33 that) is not really much different from everyone bundling the library.
34 I'd like that to improve, but for now it's time for a pragmatic solution
35 to this IMHO.
36
37 Paweł

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies