[opensuse-factory] Chromium browser has changed it's home location
Dear openSUSE users, Since this morning, the Chromium browser will no longer be maintained on the openSUSE OBS, nor will it be provided together with the openSUSE distribution. Instead the Chromium browser will be build on Packman and be available for the already supported openSUSE versions. This new version will replace the chromium-ffmpeg package that was already delivered through Packman. In the next days, I will delete the Chromium package from it's home location network:chromium and also send a delete request to openSUSE:Factory. The reason for this change is that ffmpeg support is becoming more and more integrated with the browser itself, making it very hard to remove the ffmpeg related sourcefiles and still keeping a workable browser. In the last few weeks, I tried everything to keep Chromium part of the openSUSE distribution but unfortunately I failed. And as we all know ffmpeg is one of those packages that are not allowed to be present on the openSUSE OBS. Therefore the only logical decision was to move Chromium completely to Packman. The new package will be a full enabled Chromium with build-in support for ffmpeg. The new version 25.0.1329 is already available from Packman and should be installed automatically as that it replaces the chromium-ffmpeg package. If not, please check manually in order to get the latest version from Packman. This should be a one-time manual intervention. Regards Raymond Community Maintainer for the openSUSE Chromium package -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 19.11.2012 08:16, Raymond Wooninck wrote:
Dear openSUSE users,
Since this morning, the Chromium browser will no longer be maintained on the openSUSE OBS, nor will it be provided together with the openSUSE distribution.
Instead the Chromium browser will be build on Packman and be available for the already supported openSUSE versions. This new version will replace the chromium-ffmpeg package that was already delivered through Packman.
In the next days, I will delete the Chromium package from it's home location network:chromium and also send a delete request to openSUSE:Factory.
The reason for this change is that ffmpeg support is becoming more and more integrated with the browser itself, making it very hard to remove the ffmpeg related sourcefiles and still keeping a workable browser. In the last few weeks, I tried everything to keep Chromium part of the openSUSE distribution but unfortunately I failed. And as we all know ffmpeg is one of those packages that are not allowed to be present on the openSUSE OBS. Therefore the only logical decision was to move Chromium completely to Packman. The new package will be a full enabled Chromium with build-in support for ffmpeg.
The usual question arises: what are other distributions are doing? Chromium is pretty popular there too I suppose. We can't have ffmpeg sources on OBS, but what exactly does chromium need to compile in OBS? Would a ffmpeg stub package be sufficient? Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 20 November 2012 08:51, Stephan Kulow
On 19.11.2012 08:16, Raymond Wooninck wrote:
Dear openSUSE users,
Since this morning, the Chromium browser will no longer be maintained on the openSUSE OBS, nor will it be provided together with the openSUSE distribution.
Instead the Chromium browser will be build on Packman and be available for the already supported openSUSE versions. This new version will replace the chromium-ffmpeg package that was already delivered through Packman.
In the next days, I will delete the Chromium package from it's home location network:chromium and also send a delete request to openSUSE:Factory.
The reason for this change is that ffmpeg support is becoming more and more integrated with the browser itself, making it very hard to remove the ffmpeg related sourcefiles and still keeping a workable browser. In the last few weeks, I tried everything to keep Chromium part of the openSUSE distribution but unfortunately I failed. And as we all know ffmpeg is one of those packages that are not allowed to be present on the openSUSE OBS. Therefore the only logical decision was to move Chromium completely to Packman. The new package will be a full enabled Chromium with build-in support for ffmpeg.
The usual question arises: what are other distributions are doing? Chromium is pretty popular there too I suppose.
Well it looks like Fedora do NOT have the Chromium browser in their hosted repos - their equivalent to OBS. Ubuntu do have Chromium as part of their Universe repo, but their repo layout is somewhat confusing to say the least from a legal perspective.
We can't have ffmpeg sources on OBS, but what exactly does chromium need to compile in OBS? Would a ffmpeg stub package be sufficient?
Regards, Andy -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 20 November 2012 09:07:13 Andrew Wafaa wrote:
The usual question arises: what are other distributions are doing? Chromium is pretty popular there too I suppose.
Well it looks like Fedora do NOT have the Chromium browser in their hosted repos - their equivalent to OBS. Ubuntu do have Chromium as part of their Universe repo, but their repo layout is somewhat confusing to say the least from a legal perspective.
It depends here on how the distributions are handling the difficult packages like ffmpeg. The distibutions, like openSUSE and Fedora, who avoid these packages also do not package Chromium. openSUSE was the only one who did that patching and made Chromium build without ffmpeg (and have the necessary ffmpeg package coming from Packman). As Andrew indicated those that handle ffmpeg differently, like Ubuntu, are packaging ffmpeg and Chromium. What was mentioned in the past also is that the Chrome browser is also provided for openSUSE by one of the Google repositories. This was also indicated on a previous discussion on this mailinglist.
We can't have ffmpeg sources on OBS, but what exactly does chromium need to compile in OBS? Would a ffmpeg stub package be sufficient?
I have tried to use the libffmpeg-devel package from RedDwarf, but this crashed due to incompatibility with the ffmpeg changes within the Chromium source. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Stephan Kulow wrote:
On 19.11.2012 08:16, Raymond Wooninck wrote:
Since this morning, the Chromium browser will no longer be maintained on the openSUSE OBS, nor will it be provided together with the openSUSE distribution.
Instead the Chromium browser will be build on Packman and be available for the already supported openSUSE versions. This new version will replace the chromium-ffmpeg package that was already delivered through Packman.
In the next days, I will delete the Chromium package from it's home location network:chromium and also send a delete request to openSUSE:Factory.
The reason for this change is that ffmpeg support is becoming more and more integrated with the browser itself, making it very hard to remove the ffmpeg related sourcefiles and still keeping a workable browser. In the last few weeks, I tried everything to keep Chromium part of the openSUSE distribution but unfortunately I failed. And as we all know ffmpeg is one of those packages that are not allowed to be present on the openSUSE OBS. Therefore the only logical decision was to move Chromium completely to Packman. The new package will be a full enabled Chromium with build-in support for ffmpeg.
The usual question arises: what are other distributions are doing? Chromium is pretty popular there too I suppose.
We can't have ffmpeg sources on OBS, but what exactly does chromium need
I doubt it's that black and white. We just need to make absolutely sure that no problematic parts end up in a package. It should be fine to build chromium against its internal ffmpeg copy. AFAICS there is even a build mode that just uses the headers. To make sure it never can build in another mode the .spec file could even rm -rf the not needed parts of the source before 'make'. However, chromium actually only seems to use codecs we have in the distro anyways. The config.h in there has this (linebreaks added for readability): #define FFMPEG_CONFIGURATION \ "--disable-everything \ --disable-avdevice \ --disable-avfilter \ --disable-bzlib \ --disable-doc \ --disable-network \ --disable-postproc \ --disable-swresample \ --disable-swscale \ --disable-zlib \ --enable-fft \ --enable-rdft \ --enable-shared \ --disable-dxva2 \ --disable-vaapi \ --disable-vda \ --disable-vdpau \ --optflags=-O2 \ --enable-decoder='theora,vorbis,vp8' \ --enable-decoder='pcm_u8,pcm_s16le,pcm_s24le,pcm_f32le' \ --enable-decoder='pcm_s16be,pcm_s24be' \ --enable-demuxer='ogg,matroska,wav' \ --enable-parser='vp3,vorbis,vp8' \ --enable-pic" So I guess there are even chances that an included ffmpeg configured in such a restricted way could be acceptable. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, 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 Nov 20, 12 11:31:38 +0100, Ludwig Nussel wrote:
Stephan Kulow wrote:
We can't have ffmpeg sources on OBS, but what exactly does chromium need
It should be fine to build chromium against its internal ffmpeg copy. [...] However, chromium actually only seems to use codecs we have in the distro anyways. [...] So I guess there are even chances that an included ffmpeg configured in such a restricted way could be acceptable.
Two restrictions come to my mind: 1) this should be called by a differnet name: ffmpeg-chromium or ffmpeg-free or similar, to a) avoid confusion with a full featured ffmpeg. b) allow the legal team to handle this differently. 2) The stock ffmpeg source tar ball does not appear in obs, but the ffmpeg-chromium binary is available in obs. Restriction 2 might be doable with sources in ibs and some clever tunneling? Publish off, Use for build on, or something? cheers, JW- -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de back to ascii! __/ _---|____________\/ \ | 0911 74053-508 say #263A!__/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Jeff Hawn, J.Guild, F.Imendoerffer, HRB 16746 (AG Nuernberg), Maxfeldstrasse 5, 90409 Nuernberg, Germany SuSE. Supporting Linux since 1992. ☺ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andrew Wafaa -
Juergen Weigert -
Ludwig Nussel -
Raymond Wooninck -
Stephan Kulow