Fwd: [opensuse-buildservice] I suspect that my chromium package build is going wrong
---------- Forwarded message ----------
From: James Bond
Currently network:chromium builds indeed the chromium package for openSUSE distro's, but it doesn't any SUSE specific patches, etc to the source tarball.
I see chromium 31 there, chromium in debian repository is an older version. chromedriver is tricky since it has requirements about the version of chromium. A version (or a few versions) mismatch between chromedriver and chromium can lead to chromedriver not working at all with that version of chromium. I know this for a fact since I've bumped into this problem while trying to get them to work in another linux distribution. That's why I have thought it is a good idea to attempt building chromedriver from the same version of source code that was used to build the chromium package for the debian repository.
If I understood you correctly, then the only thing you want is to build the chromedriver?
Correct. As stated above, there's no chromedriver package in the debian repository (and I don't know why, it would be so much easier if chromedriver would be just one apt-get install command away!).
If that is correct, then why do you build the full chromium build?
I have looked for hints here:
http://packages.ubuntu.com/raring/chromium-chromedriver . This is the
chromedriver package for ubuntu, yet chrome is specified as build
target in rules file. I am just trying to guide myself using reasons
that look like common sense to me, I have zero prior experience
building debian packages. To me, just adding chromedriver as
additional target looked like the minimum change I have to make
manually to the build scripts.
2013/10/1 Raymond Wooninck
On Tuesday 01 October 2013 15:16:51 James Bond wrote:
correct me if I'm making a wrong assumption) that openSUSE:Factory is a project that builds packages for OpenSUSE and network:chromium is a project for building Linux binaries that are distribution agnostic. My
Currently network:chromium builds indeed the chromium package for openSUSE distro's, but it doesn't any SUSE specific patches, etc to the source tarball.
project is making use of the vanilla source code chromium tarball + Debian patches and is trying to build a package for the 32bit Debian Wheezy - same version of chromium as the one in the repository, the only difference between it and the chromium package from the Debian repository being that I'm trying to also compile chromedriver and bundle it into the package.
If I understood you correctly, then the only thing you want is to build the chromedriver ? If that is correct, then why do you build the full chromium build ? Building chromium will not give you the chromedriver as that this need to be explicitly indicated and build separately. The outcome of the chromedriver build is a single executable which could be packaged separately (same as happens on openSUSE). You can then decide whether or not to install that particular package.
Regards
Raymond -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 01 October 2013 20:04:52 James Bond wrote:
I see chromium 31 there, chromium in debian repository is an older version. chromedriver is tricky since it has requirements about the
In the past we have been tracking svn snapshots in a similar way as that you tried to build Chromium in your repo. However I got the hint to start using the official released tarballs in order to track a more stable version of chromium. The target is to track the Beta-channel, but for I can do this the Beta channel has to go to version 31 first.
If that is correct, then why do you build the full chromium build?
I have looked for hints here: http://packages.ubuntu.com/raring/chromium-chromedriver . This is the chromedriver package for ubuntu, yet chrome is specified as build target in rules file. I am just trying to guide myself using reasons
Why don't you have a look at the chromium.spec file in network:chromium. This spec-file will set-up the build itself and initializes chromium for the right build. Once that setup is done, I am initiating three stages of building, namely: ninja -c out/Release chromium which builds the webbrowser ninja -c out/Release chrome_sandbox which builds the suid-sandbox ninja -c out/Release chromedriver which build the chromedriver. So the only that you should do in your package is to unpack the tarball of the debian package, setup the chromium builddir and then to issue the command to build the chromedriver. This build should take about a 15 minutes and doesn't require a lot of memory either. Once it build, you have to move the binary chromedriver for the out/Release directory to the place where you want it to be and that;s it. Regards Raymond -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
James Bond -
Raymond Wooninck