On Sun, Sep 22, 2013 at 5:17 PM, Paweł Hajdan, Jr.
phajdan...@gentoo.org wrote:
I'd like to get your feedback and opinion about removing shared v8
library package from Gentoo.
The three inside the box options require hope:
1. Use share lib. Hope upstream package devs code to whichever V8 API
On 09/23/2013 05:48 AM, Michał Górny wrote:
Dnia 2013-09-22, o godz. 17:17:53
Paweł Hajdan, Jr. phajdan...@gentoo.org napisał(a):
I'd like maintainers of all packages depending on dev-lang/v8 to make
their packages use bundled v8 copy instead (I can file bugs for that,
let's discuss here
On 10/6/13 12:05 AM, Chris Stankevitz wrote:
On Sun, Sep 22, 2013 at 5:17 PM, Paweł Hajdan, Jr.
phajdan...@gentoo.org wrote:
I'd like to get your feedback and opinion about removing shared v8
library package from Gentoo.
The three inside the box options require hope:
1. Use share lib.
В Вт, 24/09/2013 в 11:46 -0700, Paweł Hajdan, Jr. пишет:
On 9/22/13 5:24 PM, Peter Stuge wrote:
Paweł Hajdan, Jr. wrote:
compiling with versions of v8 other than what is included is not
currently supported.
..
For now V8 upstream gives no guarantees about API/ABI stability and
On Tue, Sep 24, 2013 at 7:46 PM, Paweł Hajdan, Jr.
phajdan...@gentoo.orgwrote:
Perfect.
Seriously? Perfect because one person agrees with you?
Sigh.
Diego Elio Pettenò — Flameeyes
flamee...@flameeyes.eu — http://blog.flameeyes.eu/
On 9/25/13 2:44 AM, Diego Elio Pettenò wrote:
On Tue, Sep 24, 2013 at 7:46 PM, Paweł Hajdan, Jr.
phajdan...@gentoo.orgwrote:
Perfect.
Seriously? Perfect because one person agrees with you?
Sigh.
Look at the API breaks and talk to v8 upstream - if you have a better
solution to actual bugs
On 9/25/13 1:16 AM, Peter Volkov wrote:
But could you comment on how hard it'll be to slot v8 shared library?
Keeping libraries bundled is a security nightmare.
Slotting v8 would be hugely impractical and rather a misuse of SLOTs.
Slotting makes sense when there are at most 2-3 major versions,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 25/09/13 11:52 AM, Paweł Hajdan, Jr. wrote:
On 9/25/13 2:44 AM, Diego Elio Pettenò wrote:
On Tue, Sep 24, 2013 at 7:46 PM, Paweł Hajdan, Jr.
phajdan...@gentoo.orgwrote:
Perfect.
Seriously? Perfect because one person agrees with you?
On 9/25/13 9:01 AM, Ian Stakenvicius wrote:
However, if it's possible to keep the rest of the tree using one
system package of v8 (or very small subset), and just maintain
that(those) via security backports, would that be viable?
In the current state of v8, no.
Latest security-supported v8 is
On 9/22/13 5:24 PM, Peter Stuge wrote:
Paweł Hajdan, Jr. wrote:
compiling with versions of v8 other than what is included is not
currently supported.
..
For now V8 upstream gives no guarantees about API/ABI stability and
actually breaks it very often
I agree that it isn't worth the effort
On Mon, Sep 23, 2013 at 2:24 AM, Ian Stakenvicius a...@gentoo.org wrote:
FYI - Spidermonkey is in the exact same situation -- upstream develops
with the expectation that projects will embed the code or at best
bundle the lib. They also completely break API with every major
version bump (ie,
Dnia 2013-09-22, o godz. 17:17:53
Paweł Hajdan, Jr. phajdan...@gentoo.org napisał(a):
I'd like maintainers of all packages depending on dev-lang/v8 to make
their packages use bundled v8 copy instead (I can file bugs for that,
let's discuss here whether it should be done).
For now V8
I'd like to get your feedback and opinion about removing shared v8
library package from Gentoo. It's currently used by www-client/chromium,
dev-db/drizzle, dev-db/mongodb, dev-lang/v8cgi and sci-geosciences/osgearth.
net-libs/nodejs switched back to bundled v8 a long time ago:
25 Feb 2013;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/09/13 08:17 PM, Paweł Hajdan, Jr. wrote:
I'd like to get your feedback and opinion about removing shared v8
library package from Gentoo. It's currently used by
www-client/chromium, dev-db/drizzle, dev-db/mongodb, dev-lang/v8cgi
and
Paweł Hajdan, Jr. wrote:
compiling with versions of v8 other than what is included is not
currently supported.
..
For now V8 upstream gives no guarantees about API/ABI stability and
actually breaks it very often
I agree that it isn't worth the effort to try to offer V8 as a
library then.
As
15 matches
Mail list logo