On Sunday 07 September 2014 15:53, Yamaban wrote:

On Sun, 7 Sep 2014 15:40, Jan Engelhardt wrote:

...

On Sunday 2014-09-07 15:28, Raymond Wooninck wrote:

...

I would like to propose to drop the V8 Javascript package from Factory. As far as I know there is no other package using V8 standalone. Chromium and NodeJS are both utilizing the in-source V8 package and has no dependencies on this.

Would it be possible to make those two use the external V8? (Following "No Bundled Libraries/Programs" 'guideline')

Sadly the "working" versions of the in-source V8 differ.

You would have to bundle NodeJS and Chromium and V8 builds to successful enable a working external V8, with no guaranty of fully functional NodeJS.

In view of the Chromium update cycle, and view of NodeJS in server usage, this is NOT a good way to make friends with the NodeJS users.

In the past we had this situation and I had to do a lot of tricks in order to get a working situation with Chromium and V8 as separate packages. I know that the guidelines are not to use the bundled libraries, but if I would follow that guideline to the letter than there wouldn't be any Chromium package. I believe the current situation is that half of the required libraries are in-source and the rest is taken from the system. Trying to utilize all libraries from system delivers build errors or worse a non working binary. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 07.09.2014 um 17:49 schrieb Marcus Meissner:

On Sun, Sep 07, 2014 at 05:28:13PM +0200, Raymond Wooninck wrote:

...

On Sunday 07 September 2014 15:53, Yamaban wrote:

...

On Sun, 7 Sep 2014 15:40, Jan Engelhardt wrote:

...

On Sunday 2014-09-07 15:28, Raymond Wooninck wrote:

...

I would like to propose to drop the V8 Javascript package from Factory. As far as I know there is no other package using V8 standalone. Chromium and NodeJS are both utilizing the in-source V8 package and has no dependencies on this.

Would it be possible to make those two use the external V8? (Following "No Bundled Libraries/Programs" 'guideline')

Sadly the "working" versions of the in-source V8 differ.

You would have to bundle NodeJS and Chromium and V8 builds to successful enable a working external V8, with no guaranty of fully functional NodeJS.

In view of the Chromium update cycle, and view of NodeJS in server usage, this is NOT a good way to make friends with the NodeJS users.

In the past we had this situation and I had to do a lot of tricks in order to get a working situation with Chromium and V8 as separate packages. I know that the guidelines are not to use the bundled libraries, but if I would follow that guideline to the letter than there wouldn't be any Chromium package. I believe the current situation is that half of the required libraries are in-source and the rest is taken from the system. Trying to utilize all libraries from system delivers build errors or worse a non working binary.

In the v8 case I think its best to let nodejs and chromium have their own.

And so I am for dropping the v8 package itself.

Unfortunately iirc the v8 package was updated to support aarch64, whereas the version in nodejs does not yet. When Dirk tried updating nodejs to an unstable version that includes a suitable v8, obs-server no longer built. So if you guys want to use weird included versions, please update them so that things actually build beyond x86. Thanks, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Sunday 2014-09-07 17:28, Raymond Wooninck wrote:

...

...

Would it be possible to make those two use the external V8? (Following "No Bundled Libraries/Programs" 'guideline')

Sadly the "working" versions of the in-source V8 differ.

[...] I know that the guidelines are not to use the bundled libraries, but if I would follow that guideline to the letter than there wouldn't be any Chromium package.

It's a guideline for us, not a policy ;) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org