[opensuse-packaging] Chromium package in openSUSE releases
With openSUSE 12.1 the Chromium browser became part of the openSUSE release, after spending quite some time in the openSUSE:<release>:Contrib repositories. Unfortunately a bug report was created (bnc#731832), where an user complains that openSUSE is releasing an alpha version of the Chromium browser and that this should be a stable version. It seems that the reporter bases his statement on the fact how Ubuntu, Archlinux and Debian are handling the Chromium browser. This seems to be complete based on the Chrome browser. I did some digging of my own and I found the following webpage that explains the release management behind Chrome and Chromium (http://ftagada.wordpress.com/2011/01/19/chromium-release-management- explained/) Half way the page is the following indicated: "I (the author, an Ubuntu packager) said in the introduction that there is no such thing upstream. They have enough in their plate with just Chrome. So it is up to each downstream distribution to decide what is best for its users." So officially there are no alpha, beta or stable versions of Chromium and it is up to each dsitribution to decide what they want to ship. For openSUSE 12.1 it is too late to change anything here as that this would mean that existing users might experience loss-of-data as that their profiles are not compatible with lower versions of Chromium. However for the upcoming 12.2 release there is still time to decide which way openSUSE wants to go. At this moment I see three possibilities: 1) Keep things the way they are. Chromium will be updated regularly to the latest available version. No change from the current procedure 2) openSUSE will use the Chrome release management and the Chromium package will be frozen until the Stable version has reached the current version of Chromium. Then this is the package that will be maintained from that moment onwards. 3) We have a mixture of the above. In the Chromium devel-project (network:chromium), two packages are maintained. The first package chromium will follow the stable releases and a second package chromium-unstable will follow the current procedure and gets a weekly update. However the chromium- unstable package will never be submitted to Factory. Before making m choice in what to provide, I would like to have your feedback on how to continue this. Honestly speaking I do not like option 3 as that this would mean double the work for me, but it is a possibility. Thanks Regards Raymond (tittiatcoke) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 23.11.2011 19:10, Raymond Wooninck wrote:
1) Keep things the way they are. Chromium will be updated regularly to the latest available version. No change from the current procedure
2) openSUSE will use the Chrome release management and the Chromium package will be frozen until the Stable version has reached the current version of Chromium. Then this is the package that will be maintained from that moment onwards.
3) We have a mixture of the above. In the Chromium devel-project (network:chromium), two packages are maintained. The first package chromium will follow the stable releases and a second package chromium-unstable will follow the current procedure and gets a weekly update. However the chromium- unstable package will never be submitted to Factory.
I am fine with the way things are (1). -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
* Raymond Wooninck <tittiatcoke@gmail.com> [11-23-11 13:12]:
1) Keep things the way they are. Chromium will be updated regularly to the latest available version. No change from the current procedure ... Before making m choice in what to provide, I would like to have your feedback on how to continue this. Honestly speaking I do not like option 3 as that this would mean double the work for me, but it is a possibility.
Keeping the present way is good. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 2011-11-23 19:10:46 (+0100), Raymond Wooninck <tittiatcoke@gmail.com> wrote: [...]
So officially there are no alpha, beta or stable versions of Chromium and it is up to each dsitribution to decide what they want to ship. For openSUSE 12.1 it is too late to change anything here as that this would mean that existing users might experience loss-of-data as that their profiles are not compatible with lower versions of Chromium. However for the upcoming 12.2 release there is still time to decide which way openSUSE wants to go. At this moment I see three possibilities:
1) Keep things the way they are. Chromium will be updated regularly to the latest available version. No change from the current procedure
2) openSUSE will use the Chrome release management and the Chromium package will be frozen until the Stable version has reached the current version of Chromium. Then this is the package that will be maintained from that moment onwards.
3) We have a mixture of the above. In the Chromium devel-project (network:chromium), two packages are maintained. The first package chromium will follow the stable releases and a second package chromium-unstable will follow the current procedure and gets a weekly update. However the chromium- unstable package will never be submitted to Factory.
Before making m choice in what to provide, I would like to have your feedback on how to continue this. Honestly speaking I do not like option 3 as that this would mean double the work for me, but it is a possibility.
IMHO, the "openSUSE way" would indeed be option 3 :))) (I'd argue it's the "openSUSE way" because it's offering the choice to users, which is the choice we take in most cases.) That's pretty much the way Firefox is maintained: the stable version goes into factory and releases (and occasional updates) while the latest stable and the latest beta are available from separate repositories. But that, indeed, is a much more time consuming process. So it's up to you to see whether you'd have time for it, or whether you prefer another option. And maybe someone can step up and maintain the other "branch" of it. Ultimately, it's up to you to decide. If people don't like it, "patches are welcome" :) It's pretty easy for someone to contact you and work with you to maintain e.g. both the stable + the latest snapshots (as you already do, for the latter). In any case, thanks for the hard work :) cheers -- -o) Pascal Bleser /\\ http://opensuse.org -- we haz green _\_v http://fosdem.org -- we haz conf
Hi; On 11/23/2011 07:10 PM, Raymond Wooninck wrote:
With openSUSE 12.1 the Chromium browser became part of the openSUSE release, after spending quite some time in the openSUSE:<release>:Contrib repositories.
Unfortunately a bug report was created (bnc#731832), where an user complains that openSUSE is releasing an alpha version of the Chromium browser and that this should be a stable version. It seems that the reporter bases his statement on the fact how Ubuntu, Archlinux and Debian are handling the Chromium browser. This seems to be complete based on the Chrome browser.
I did some digging of my own and I found the following webpage that explains the release management behind Chrome and Chromium (http://ftagada.wordpress.com/2011/01/19/chromium-release-management- explained/)
Half way the page is the following indicated: "I (the author, an Ubuntu packager) said in the introduction that there is no such thing upstream. They have enough in their plate with just Chrome. So it is up to each downstream distribution to decide what is best for its users."
So officially there are no alpha, beta or stable versions of Chromium and it is up to each dsitribution to decide what they want to ship. For openSUSE 12.1 it is too late to change anything here as that this would mean that existing users might experience loss-of-data as that their profiles are not compatible with lower versions of Chromium. However for the upcoming 12.2 release there is still time to decide which way openSUSE wants to go. At this moment I see three possibilities:
1) Keep things the way they are. Chromium will be updated regularly to the latest available version. No change from the current procedure
This is the best option imho, web is moving too fast anyway. Regards. -- İsmail Dönmez - openSUSE Booster 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-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Out-of-the-box (probably bikesheddy) suggestion. Why should we build chrome by ourselves at all ? We do not have any patches made from SUSE for chromium which will be in upstream only in future releases (say like the Kernel). We can just get the latest Chrome for openSUSE from www.google.com/chrome Chrome project already gives 32-bit and 64-bit dev and beta builds for openSUSE (and fedora). We can just work with those chrome packagers instead of building it ourselves. I see no benefit in building chrome by ourselves. If we are paranoid about chrome recording few things that we do, we should ideally use a different browser, like Firefox Sankar
On 11/23/2011 at 11:40 PM, in message <4430597.lteV4vvxfT@hqvmt4xx20.eur.cchbc.com>, Raymond Wooninck <tittiatcoke@gmail.com> wrote: With openSUSE 12.1 the Chromium browser became part of the openSUSE release, after spending quite some time in the openSUSE:<release>:Contrib repositories.
Unfortunately a bug report was created (bnc#731832), where an user complains
that openSUSE is releasing an alpha version of the Chromium browser and that
this should be a stable version. It seems that the reporter bases his statement on the fact how Ubuntu, Archlinux and Debian are handling the Chromium browser. This seems to be complete based on the Chrome browser.
I did some digging of my own and I found the following webpage that explains
the release management behind Chrome and Chromium (http://ftagada.wordpress.com/2011/01/19/chromium-release-management- explained/)
Half way the page is the following indicated: "I (the author, an Ubuntu packager) said in the introduction that there is no such thing upstream. They have enough in their plate with just Chrome. So it is up to each downstream distribution to decide what is best for its users."
So officially there are no alpha, beta or stable versions of Chromium and it
is up to each dsitribution to decide what they want to ship. For openSUSE 12.1 it is too late to change anything here as that this would mean that existing
users might experience loss-of-data as that their profiles are not compatible with lower versions of Chromium. However for the upcoming 12.2 release there
is still time to decide which way openSUSE wants to go. At this moment I see
three possibilities:
1) Keep things the way they are. Chromium will be updated regularly to the latest available version. No change from the current procedure
2) openSUSE will use the Chrome release management and the Chromium package will be frozen until the Stable version has reached the current version of Chromium. Then this is the package that will be maintained from that moment onwards.
3) We have a mixture of the above. In the Chromium devel-project (network:chromium), two packages are maintained. The first package chromium will follow the stable releases and a second package chromium-unstable will follow the current procedure and gets a weekly update. However the chromium- unstable package will never be submitted to Factory.
Before making m choice in what to provide, I would like to have your feedback on how to continue this. Honestly speaking I do not like option 3 as that this would mean double the work for me, but it is a possibility.
Thanks
Regards
Raymond (tittiatcoke)
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Out-of-the-box (probably bikesheddy) suggestion. Why should we build chrome by ourselves at all ? We do not have any patches made from SUSE for chromium which will be in upstream only in future releases (say like the Kernel). We can just get the latest Chrome for openSUSE from www.google.com/chrome
Correct that we do not have any patches from ourselves, however in the past we needed to build it ourselves in order to prevent strange dependencies on non- existing packages or packageversions. Also we have changed the build process to take into account system libraries that are normally already installed on the system (e.g. zlib, jpeg, etc ) This way Chromium would be better integrated. Raymond -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 11/24/2011 at 01:49 PM, in message <3128449.01oD2kAFK0@hqvmt4xx20.eur.cchbc.com>, Raymond Wooninck <tittiatcoke@gmail.com> wrote: Out-of-the-box (probably bikesheddy) suggestion. Why should we build chrome by ourselves at all ? We do not have any patches made from SUSE for chromium
which will be in upstream only in future releases (say like the Kernel). We can just get the latest Chrome for openSUSE from www.google.com/chrome
Correct that we do not have any patches from ourselves, however in the past we needed to build it ourselves in order to prevent strange dependencies on non- existing packages or packageversions.
Also we have changed the build process to take into account system libraries
that are normally already installed on the system (e.g. zlib, jpeg, etc ) This way Chromium would be better integrated.
ah okay. But do you think it will be better if we just work with the chrome engineers who are responsible for openSUSE builds ? Since they already make seperate packages for openSUSE (instead of a generic linux rpm) they may be interested in optimizing things. Thanks for your explanation. Sankar -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Sankar P wrote:
Out-of-the-box (probably bikesheddy) suggestion. Why should we build chrome by ourselves at all ? We do not have any patches made from SUSE for chromium which will be in upstream only in future releases (say like the Kernel). We can just get the latest Chrome for openSUSE from www.google.com/chrome
Are you saying we should encourage users to install [proprietary] binary rpms from random sites on the Internet? Or are you saying we should encourage Google to maintain their openSUSE packages in Factory/update repos ie make them easily available to users and conform to our packaging policies? 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-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 11/25/2011 at 02:08 PM, in message <4ECF53F4.8020306@suse.de>, Ludwig Nussel <ludwig.nussel@suse.de> wrote: Sankar P wrote: Out-of-the-box (probably bikesheddy) suggestion. Why should we build chrome by ourselves at all ? We do not have any patches made from SUSE for chromium which will be in upstream only in future releases (say like the Kernel). We can just get the latest Chrome for openSUSE from www.google.com/chrome
Are you saying we should encourage users to install [proprietary] binary rpms from random sites on the Internet? Or are you saying we should encourage Google to maintain their openSUSE packages in Factory/update repos ie make them easily available to users and conform to our packaging policies?
We definitely can ask Google to maintain their openSUSE specific rpm build in OBS. However I doubt if they will be ready to conform to our packaging policies etc. My suggestion was the former. I agree that some may feel paranoid about installing binary rpm from a third party site. For most people, Google has a higher level of trust than some random site. Also, people already install VLC player from 3rd party site. I personally don't feel paranoid about installing chrome from Google's site. So I gave that suggestion. I agree that it may not be suitable for all. Sankar -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 11/23/2011 07:10 PM, Raymond Wooninck wrote:
is still time to decide which way openSUSE wants to go. At this moment I see three possibilities:
1) Keep things the way they are. Chromium will be updated regularly to the latest available version. No change from the current procedure
I would vote for this option, because 1) Chromium is developed really quickly and with the current type of release engineering they have I'm sure lots of security fixes are not being backported to the "stable" Chromium releases 2) who wants "rocksolid" releases could use Chrome from Google's repo 3) if there are some issues (and I know there are, but are fixed pretty quickly), let's concentrate on them and try to fix them, this way we also contribute to Chromium development -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (8)
-
Ismail Dönmez -
Ludwig Nussel -
Pascal Bleser -
Patrick Shanahan -
Pavol Rusnak -
Raymond Wooninck -
Sankar P -
Stefan Seyfried