| View previous topic :: View next topic |
| Author |
Message |
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
 Posted: Thu Oct 18, 2018 10:28 pm Post subject: Chromium - no binaries alternative, as firefox, libreoffice |
 |
|
I have had issues with emerging and building chromium in its current state for the longest while, i have raised my issue numerous times with the ebuild maintainer himself
and i am constantly hitting a wall when talking to him, what will it take for a chromium binary alternative to be available for us users who are having trouble with building this package
Just like libreoffice and firefox, bot have a binary alternative available, but it seems the chromium project runners simply refuse or are unwilling to make an ebuild for something that exists and is available
As it is building chromium is one of the longest package to build, is problematic to build and support at best for those persistent hard to find issues are ignored.
How hard would it be to make an official ebuild to have for an already available built and compiled, functional chromium package from google for the users who are simply fed up of persistently wasting time trying to build it
Especially that downloading manually, installing chromium binary from google and temp extracting it to your home folder and functional in less than 20 seconds.
The main question i am curious about, is how many users if they had an official choice, not one forced on us, to be able to NOT have to build chromium and waste so much time on something that is obviously not working 100% in its current state |
|
| Back to top |
|
 |
Muso
Veteran
Joined: 22 Oct 2002
Posts: 1052
Location: The Holy city of Honolulu
|
| Posted: Thu Oct 18, 2018 11:13 pm Post subject: |
|
|
Have you looked into the overlays? One might have a chromium-bin.
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop! |
|
| Back to top |
|
|
ct85711
Veteran
Joined: 27 Sep 2005
Posts: 1791
|
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Thu Oct 18, 2018 11:33 pm Post subject: |
|
|
There only seems to be
www-client/ungoogled-chromium-bin
which strips stuff and is not directly unmodified from google |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21631
|
| Posted: Fri Oct 19, 2018 1:58 am Post subject: Re: Chromium - no binaries alternative, as firefox, libreoff |
|
|
| maolang wrote: | | I have had issues with emerging and building chromium in its current state for the longest while, i have raised my issue numerous times with the ebuild maintainer himself |
Are the issues with the Gentoo ebuild or with the upstream code? Some Gentoo maintainers are not able to support the upstream code, so if this is a generic problem with Chromium, contacting the ebuild maintainer may not help you. | maolang wrote: | | and i am constantly hitting a wall when talking to him, what will it take for a chromium binary alternative to be available for us users who are having trouble with building this package |
Someone will need to build it, post it for public download, and make available an ebuild to download that public copy. Additionally, that public copy will need to exclude any components that are not freely redistributable. | maolang wrote: | | but it seems the chromium project runners simply refuse or are unwilling to make an ebuild for something that exists and is available |
Where is this prebuilt Chromium available? I recall seeing a prior thread about this, where it was concluded that upstream was releasing so often that it was infeasible for the Gentoo maintainers to provide -bin packages. | maolang wrote: | | support at best for those persistent hard to find issues are ignored. |
Could you link to the bug reports that were ignored? | maolang wrote: | | How hard would it be to make an official ebuild to have for an already available built and compiled, functional chromium package from google for the users who are simply fed up of persistently wasting time trying to build it |
This should be pretty easy, if upstream has already built it and provided an acceptable download. Post a link to it and someone here can probably write a simple ebuild for it. | maolang wrote: | | Especially that downloading manually, installing chromium binary from google and temp extracting it to your home folder and functional in less than 20 seconds. |
Extracting to the home folder is always wrong, and should not even work if your system is configured correctly. Your home directory should be noexec, in which case it cannot be run from there. |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Fri Oct 19, 2018 2:59 am Post subject: |
|
|
| Quote: | | Someone will need to build it, post it for public download, and make available an ebuild to download that public copy. Additionally, that public copy will need to exclude any components that are not freely redistributable. |
Its a zip file so no building required...
For this specific one, this would be considered as chromium-bin-9999
just as when you look in the ebuilds for chromium, google-chrome-beta and unstable
Chromium Source:
SRC_URI="https://commondatastorage.googleapis.com/chromium-browser-official/${P}.tar.xz"
Google Chrome:
SRC_URI="https://dl.google.com/linux/chrome/deb/pool/main/g/${MY_PN}/${MY_P}_amd64.deb"
| Quote: | | Where is this prebuilt Chromium available? I recall seeing a prior thread about this, where it was concluded that upstream was releasing so often that it was infeasible for the Gentoo maintainers to provide -bin packages. |
Chromium Built: Direct link, surely easy to figure out specific versions
wget -O chromium-linux.zip https://download-chromium.appspot.com/dl/Linux_x64?type=snapshots
| Quote: | | Extracting to the home folder is always wrong, and should not even work if your system is configured correctly. Your home directory should be noexec, in which case it cannot be run from there. |
Just as in #gentoo they mention if you are going to install something outside of portage / emerge, you should use your home directory which in this case i am
On this just extract it in ~/chromium and chmod +x chrome, chrome_sandbox
Then if i dont have a shortcut for it, make one...
echo '
[Desktop Entry]
Name=Chromium-Binary
Type=Application
Comment=Open-source version of Google Chrome web browser
Exec=/home/denis/chromium/chrome %U
Terminal=false
TryExec=/home/denis/chromium/chrome
Icon=chromium-browser
Categories=Network;WebBrowser;
MimeType=text/html;text/xml;application/xhtml+xml;x-scheme-handler/http;x-scheme-handler/https;x-scheme-handler/ftp;x-scheme-handler/mailto;x-scheme-handler/webcal;
StartupWMClass=chromium-browser
Actions=new-window;new-private-window;
[Desktop Action new-window]
Name=New Window
Exec=/home/denis/chromium/chrome
[Desktop Action new-private-window]
Name=New Incognito Window
Exec=/home/denis/chromium/chrome --incognito
' > /home/denis/.local/share/applications/chromium-binary.desktop
| Quote: | | Could you link to the bug reports that were ignored? |
Thats one by someone else:
https://bugs.gentoo.org/668370
There are many can't remember but this has been going on since branch version 67.... and we are now on 70 and 71 is masked and as there mentions on removing 69 soon, so this is kinda funny removing a branch while leaving only 70, 71 which i cannot build, i can build only 69 at the moment but only by hacking the current ebuild for it to un-force it from building with clang, now i got 3400+ packages installed on this system and the only one i cannot build is chromium and i get told you have something seriously wrong with your system... |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21631
|
| Posted: Fri Oct 19, 2018 3:52 am Post subject: |
|
|
That report received a response from someone who appears to be a Gentoo maintainer for the relevant package. The first response came 4 days after the ticket was filed, and provided a very reasonable explanation for why the maintainer did not immediately change the ebuild. Subsequent responses came within a day of the non-maintainer's comment that provoked a response. I will grant that 4 days is a slow turnaround compared to the forums, but on the other hand, that's 4 days until the authoritative answer from the maintainer comes down. The forums can be much more responsive because we have a large group of regular users who are knowledgeable about many of the problems routinely reported, so even if a few are out on vacation or busy with their private lives, many others are available to step in. The Chrome/Chromium package has a much smaller team. When you said the report was ignored, I thought you meant that the report received either no responses at all, or only boilerplate responses (such as requests for additional system information).
Yes, the people in #gentoo are correct that you should not install things system-wide outside of Portage. However, I maintain that your home directory should be noexec unless you have a specific development-related need for it to be otherwise. If it is noexec, running the browser there cannot work. |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Fri Oct 19, 2018 4:07 am Post subject: |
|
|
I would not be using the home directory as for in this case i have no choice...
As mentioned by the maintainer of the chromium package
| Quote: | | I already maintain ebuilds for a pre-built version of Chromium - it's called www-client/google-chrome. I don't see any reason to maintain an inferior binary package based on developer builds of Chromium. |
One easy reason is called time spent failing to build the package... |
|
| Back to top |
|
|
Genone
Retired Dev
Joined: 14 Mar 2003
Posts: 9527
Location: beyond the rim
|
| Posted: Fri Oct 19, 2018 10:34 am Post subject: |
|
|
| maolang wrote: | | For this specific one, this would be considered as chromium-bin-9999 |
-bin and -9999 don't work well together. If you define a SRC_URI you'll have to provide the corresponding checksum for the file in the Manifest. If you're using an unversioned URI as SRC_URI that checksum will be incorrect as soon as the content of the URI changes.
You haven't really explained yet why you need another package beside www-client/ungoogled-chromium-bin and www-client/google-chrome. |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Fri Oct 19, 2018 3:09 pm Post subject: |
|
|
| Quote: | -bin and -9999 don't work well together. If you define a SRC_URI you'll have to provide the corresponding checksum for the file in the Manifest. If you're using an unversioned URI as SRC_URI that checksum will be incorrect as soon as the content of the URI changes.
You haven't really explained yet why you |
The link for a -9999 was an example, surely I think you would understand what I meant as an example, when I put in the other SRC_URI as example
I think I was pretty clear why I need it, because in its current form I am unable to build it and already wasted terrible amounts of time on this, the ungoogogled one is an old version in case you have not noticed...
Do I really need to explain why I need something???
I have been battling this issue with this package and inability to build it naturally over 6-8 months now, since the 67 branch we are now on 70, I have exhausted my patience to keep trying building this **un-build-able ** package, it seems I am asking the impossible, I really don't understand the sheer resistance in having in having such unwillingness to have a solution for this issue when there is an existing one as mentioned for the main other browser Firefox and libre office suite, and those don't even come close in how long they take to build compared to chromium... |
|
| Back to top |
|
|
Goverp
Advocate
Joined: 07 Mar 2007
Posts: 2006
|
| Posted: Fri Oct 19, 2018 4:37 pm Post subject: |
|
|
| maolang wrote: | I would not be using the home directory as for in this case i have no choice...
As mentioned by the maintainer of the chromium package
| Quote: | | I already maintain ebuilds for a pre-built version of Chromium - it's called www-client/google-chrome. I don't see any reason to maintain an inferior binary package based on developer builds of Chromium. |
One easy reason is called time spent failing to build the package... |
You seem to have missed the point (repeatedly). www-client/google-chrome is a binary build (specifically a Debian package). www-client/google-chromium is the one that takes forever to build.
google-chrome took about 1 minute to emerge and a further 40 seconds to install on my machine (where /var is on a different filesystem to /usr), no building required.
_________________
Greybeard |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Fri Oct 19, 2018 4:56 pm Post subject: |
|
|
| Quote: | You seem to have missed the point (repeatedly). www-client/google-chrome is a binary build (specifically a Debian package). www-client/google-chromium is the one that takes forever to build.
google-chrome took about 1 minute to emerge and a further 40 seconds to install on my machine (where /var is on a different filesystem to /usr), no building required. |
Seems you are missing the point even more, the issue here is not chrome, but chromium on other distros, its available as well as chrome is, except here its available but un-buildable, it really seems there is a hard case of understanding by some over here of this situation, it seems it is more important to persist on refusing to accept that for such a package as chromium, that just as firefox or libreoffice some might prefer a solution that does not take 6 hours to build, to a degree i would be ok still being forced to build it, but to a point when the only choice is use a binary cause the actual solution is broken and will persist at failing to build
What must i do if i want to use chromium, must i be forced to move to another distro where a binary solution is available for it or can we get a binary solution officially created and have this issue sorted and move on to more important things afterwards |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Fri Oct 19, 2018 7:08 pm Post subject: |
|
|
| Code: | * Package: www-client/chromium-bin-9999
* Repository: maolang
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux l10n_de l10n_fr l10n_ru suid userland_GNU widevine
* FEATURES: preserve-libs sandbox selinux sesandbox userpriv usersandbox
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found sources for kernel version:
* 4.14.75-gentoo
* Checking for suitable kernel configuration options...
* Final size of build directory: 280008 KiB (273.4 MiB)
* Final size of installed tree: 264868 KiB (258.6 MiB)
* Updating icons cache ...
* Updating .desktop files database ...
* >>> SetUID: [chmod go-r] /opt/chromium-browser/chrome-sandbox ...
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date. |
[Moderator edit: added [code] tags to preserve output layout. -Hu] |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Fri Oct 19, 2018 7:11 pm Post subject: |
|
|
While we continue debating the need to add a chromium-bin alternative to the current chromium, i have a working solution
Thanks in big parts to the ungoogled-chromium-bin ebuild which i used as base to get this working |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Fri Oct 19, 2018 7:21 pm Post subject: |
|
|
| Code: | ldd /opt/chromium-browser/chrome
linux-vdso.so.1 (0x00007ffdb0579000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f7819670000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f781964e000)
librt.so.1 => /lib64/librt.so.1 (0x00007f7819644000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f78194fc000)
libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x00007f78194f9000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f78194ce000)
libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007f78194c8000)
libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007f78194bc000)
libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007f78194b8000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f78194a4000)
libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f781949d000)
libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007f781948a000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f781947c000)
libXtst.so.6 => /usr/lib64/libXtst.so.6 (0x00007f7819475000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f7819420000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f7819305000)
libnss3.so => /usr/lib64/libnss3.so (0x00007f78191d7000)
libnssutil3.so => /usr/lib64/libnssutil3.so (0x00007f78191a6000)
libsmime3.so => /usr/lib64/libsmime3.so (0x00007f781917c000)
libnspr4.so => /usr/lib64/libnspr4.so (0x00007f781913a000)
libcups.so.2 => /usr/lib64/libcups.so.2 (0x00007f78190a8000)
libdbus-1.so.3 => /usr/lib64/libdbus-1.so.3 (0x00007f781905e000)
libXss.so.1 => /usr/lib64/libXss.so.1 (0x00007f7819059000)
libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f781901d000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f7819012000)
libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007f7819005000)
libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007f7818e5c000)
libm.so.6 => /lib64/libm.so.6 (0x00007f7818cc9000)
libasound.so.2 => /usr/lib64/libasound.so.2 (0x00007f7818bd8000)
libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007f7818bca000)
libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007f7818b80000)
libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007f7818a4e000)
libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007f7818a26000)
libatk-bridge-2.0.so.0 => /usr/lib64/libatk-bridge-2.0.so.0 (0x00007f78189f6000)
libatspi.so.0 => /usr/lib64/libatspi.so.0 (0x00007f78189c2000)
libgtk-3.so.0 => /usr/lib64/libgtk-3.so.0 (0x00007f7818275000)
libgdk-3.so.0 => /usr/lib64/libgdk-3.so.0 (0x00007f78181b8000)
libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007f7818192000)
libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/libgcc_s.so.1 (0x00007f7818178000)
libc.so.6 => /lib64/libc.so.6 (0x00007f7817fad000)
/lib64/ld-linux-x86-64.so.2 (0x00007f782280c000)
libgomp.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/8.2.0/libgomp.so.1 (0x00007f7817f7e000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f7817f79000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f7817f70000)
libffi.so.7 => /usr/lib64/libffi.so.7 (0x00007f7817f65000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f7817eef000)
libplc4.so => /usr/lib64/libplc4.so (0x00007f7817ee9000)
libplds4.so => /usr/lib64/libplds4.so (0x00007f7817ee4000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2 (0x00007f7817e94000)
libgnutls.so.30 => /usr/lib64/libgnutls.so.30 (0x00007f7817d58000)
libavahi-common.so.3 => /usr/lib64/libavahi-common.so.3 (0x00007f7817d4a000)
libavahi-client.so.3 => /usr/lib64/libavahi-client.so.3 (0x00007f7817d38000)
libz.so.1 => /lib64/libz.so.1 (0x00007f7817d1f000)
libsystemd.so.0 => /lib64/libsystemd.so.0 (0x00007f7817c80000)
libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007f7817c79000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f7817c4f000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f7817c36000)
libmount.so.1 => /lib64/libmount.so.1 (0x00007f7817bda000)
libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007f7817bc3000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007f7817b7d000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f7817ab2000)
libfribidi.so.0 => /usr/lib64/libfribidi.so.0 (0x00007f7817a94000)
libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007f78179d6000)
libEGL.so.1 => /usr/lib64/opengl/nvidia/lib/libEGL.so.1 (0x00007f78177c4000)
libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007f7817785000)
libxcb-shm.so.0 => /usr/lib64/libxcb-shm.so.0 (0x00007f7817780000)
libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007f781776d000)
libGL.so.1 => /usr/lib64/opengl/nvidia/lib/libGL.so.1 (0x00007f78174c9000)
libcairo-gobject.so.2 => /usr/lib64/libcairo-gobject.so.2 (0x00007f78174bf000)
libepoxy.so.0 => /usr/lib64/libepoxy.so.0 (0x00007f781738b000)
libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007f78172c7000)
libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007f78172c1000)
libbsd.so.0 => /usr/lib64/libbsd.so.0 (0x00007f78172a5000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x00007f78171c7000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x00007f7817191000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f781718c000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0 (0x00007f781717d000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f7817177000)
libunistring.so.2 => /usr/lib64/libunistring.so.2 (0x00007f7816fef000)
libtasn1.so.6 => /usr/lib64/libtasn1.so.6 (0x00007f7816fdb000)
libnettle.so.6 => /usr/lib64/libnettle.so.6 (0x00007f7816fa0000)
libhogweed.so.4 => /usr/lib64/libhogweed.so.4 (0x00007f7816f68000)
libgmp.so.10 => /usr/lib64/libgmp.so.10 (0x00007f7816ed7000)
libidn2.so.0 => /usr/lib64/libidn2.so.0 (0x00007f7816eb9000)
liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f7816e90000)
liblz4.so.1 => /usr/lib64/liblz4.so.1 (0x00007f7816e6a000)
libcap.so.2 => /lib64/libcap.so.2 (0x00007f7816e63000)
libgcrypt.so.20 => /usr/lib64/libgcrypt.so.20 (0x00007f7816d39000)
libblkid.so.1 => /lib64/libblkid.so.1 (0x00007f7816ce4000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f7816cd1000)
libGLdispatch.so.0 => /usr/lib64/opengl/nvidia/lib/libGLdispatch.so.0 (0x00007f7816a03000)
libGLX.so.0 => /usr/lib64/opengl/nvidia/lib/libGLX.so.0 (0x00007f78167d3000)
libgraphite2.so.3 => /usr/lib64/libgraphite2.so.3 (0x00007f78167ad000)
libgpg-error.so.0 => /usr/lib64/libgpg-error.so.0 (0x00007f7816789000) |
[Moderator edit: added [code] tags to preserve output layout. -Hu] |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21631
|
| Posted: Fri Oct 19, 2018 11:30 pm Post subject: |
|
|
| maolang wrote: | | Quote: | -bin and -9999 don't work well together. If you define a SRC_URI you'll have to provide the corresponding checksum for the file in the Manifest. If you're using an unversioned URI as SRC_URI that checksum will be incorrect as soon as the content of the URI changes.
You haven't really explained yet why you |
The link for a -9999 was an example, surely I think you would understand what I meant as an example, when I put in the other SRC_URI as example |
He might have understood it, but from experience, inferring other people's intent is usually a bad idea. He went with what you had clearly articulated. The second SRC_URI is likely what caught his attention. It is explicitly unversioned, which is bad for automated download agents. | maolang wrote: | I think I was pretty clear why I need it, because in its current form I am unable to build it and already wasted terrible amounts of time on this, the ungoogogled one is an old version in case you have not noticed...
Do I really need to explain why I need something??? |
Yes, you should explain your problem, not your solution. Again from experience, people frequently encounter a problem, decide on what they think the solution should be, then ask us how to implement that solution. In many cases, a different solution would be better. When the problem is described, rather than the solution, we can identify an appropriate solution. | maolang wrote: | | I have exhausted my patience to keep trying building this **un-build-able ** package |
So switch to a better browser, that isn't constantly broken?
| maolang wrote: | | While we continue debating the need to add a chromium-bin alternative to the current chromium, i have a working solution |
Since you believe this is generally useful, perhaps you could share your work so that it is generally available to other people who want this? |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Sat Oct 20, 2018 12:44 am Post subject: |
|
|
the ebuild as it is which works, based on the ungoogled-chromium-bin
| Code: | # Copyright 1999-2018 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI="6"
CHROMIUM_LANGS="
am ar bg bn ca cs da de el en-GB en-US es-419 es et fa fi fil fr gu he hi hr
hu id it ja kn ko lt lv ml mr ms nb nl pl pt-BR pt-PT ro ru sk sl sr sv sw
ta te th tr uk vi zh-CN zh-TW
"
inherit chromium-2 gnome2-utils readme.gentoo-r1 xdg-utils
MY_PV="${PV/-r2/}-2"
MY_PN="${PN/-bin}"
MY_P="chrome-linux"
DESCRIPTION="Chromium Binary (No painfull building required)"
HOMEPAGE="https://download-chromium.appspot.com"
SRC_URI="https://download-chromium.appspot.com/dl/Linux_x64?type=snapshots -> chromium-browser.zip"
LICENSE="BSD"
SLOT="0"
KEYWORDS="-* ~amd64"
IUSE="+suid widevine"
RDEPEND="
app-accessibility/at-spi2-atk:2
app-arch/bzip2
dev-libs/atk
dev-libs/expat
dev-libs/glib:2
dev-libs/libxslt
dev-libs/nspr
>=dev-libs/nss-3.26
>=dev-libs/re2-0.2016.05.01
>=media-libs/alsa-lib-1.0.19
media-libs/fontconfig
media-libs/freetype
>=media-libs/harfbuzz-1.6.0
media-libs/libjpeg-turbo
media-libs/libpng
>=net-print/cups-1.3.11
sys-apps/dbus
sys-apps/pciutils
virtual/opengl
virtual/ttf-fonts
virtual/udev
widevine? ( www-plugins/chrome-binary-plugins:unstable[widevine(-)] )
!www-client/chromium
x11-libs/cairo
x11-libs/gdk-pixbuf:2
x11-libs/gtk+:3[X]
>=x11-libs/libva-2.2.0
x11-libs/libX11
x11-libs/libXcomposite
x11-libs/libXcursor
x11-libs/libXdamage
x11-libs/libXext
x11-libs/libXfixes
>=x11-libs/libXi-1.6.0
x11-libs/libXrandr
x11-libs/libXrender
x11-libs/libXScrnSaver
x11-libs/libXtst
x11-libs/pango
x11-misc/xdg-utils
"
DEPEND=""
DISABLE_AUTOFORMATTING="yes"
DOC_CONTENTS="
Some web pages may require additional fonts to display properly.
Try installing some of the following packages if some characters
are not displayed properly:
- media-fonts/arphicfonts
- media-fonts/droid
- media-fonts/ipamonafont
- media-fonts/noto
- media-fonts/ja-ipafonts
- media-fonts/takao-fonts
- media-fonts/wqy-microhei
- media-fonts/wqy-zenhei
To fix broken icons on the Downloads page, you should install an icon
theme that covers the appropriate MIME types, and configure this as your
GTK+ icon theme.
"
QA_PREBUILT="*"
S="${WORKDIR}/${MY_P}"
pkg_pretend() {
# Protect against people using autounmask overzealously
use amd64 || die "${PN} only works on amd64"
}
pkg_setup() {
chromium_suid_sandbox_check_kernel_config
}
src_unpack() {
default
}
src_install() {
local CHROMIUM_HOME="/opt/chromium-browser"
exeinto "${CHROMIUM_HOME}"
doexe chrome
if use suid; then
newexe chrome_sandbox chrome-sandbox
fperms 4755 "${CHROMIUM_HOME}/chrome-sandbox"
fi
if use widevine; then
dosym "../../usr/$(get_libdir)/chromium/libwidevinecdm.so" \
"${CHROMIUM_HOME}/libwidevinecdm.so"
fi
# Not using and not there si disabling it
# doexe chromedriver
newexe "${FILESDIR}/chromium-launcher-r3.sh" chromium-launcher.sh
sed -i "s:/usr/lib/:/usr/$(get_libdir)/:g" \
"${ED%/}${CHROMIUM_HOME}/chromium-launcher.sh" || die
# It is important that we name the target "chromium-browser",
# xdg-utils expect it (bug #355517)
dosym "${CHROMIUM_HOME}/chromium-launcher.sh" /usr/bin/chromium-browser
# keep the old symlink around for consistency
dosym "${CHROMIUM_HOME}/chromium-launcher.sh" /usr/bin/chromium
# Not creating a shortcut for something not there
# dosym "${CHROMIUM_HOME}/chromedriver" /usr/bin/chromedriver
# Allow users to override command-line options (bug #357629)
insinto /etc/chromium
newins "${FILESDIR}/chromium.default" "default"
pushd locales > /dev/null || die
chromium_remove_language_paks
popd > /dev/null || die
insinto "${CHROMIUM_HOME}"
doins ./*.bin
doins ./*.pak
doins ./*.so
doins icudtl.dat
doins -r locales
doins -r resources
# Install icons and desktop entry
newicon -s 48 "product_logo_48.png" chromium-browser.png
local mime_types="text/html;text/xml;application/xhtml+xml;"
mime_types+="x-scheme-handler/http;x-scheme-handler/https;" # bug #360797
mime_types+="x-scheme-handler/ftp;" # bug #412185
mime_types+="x-scheme-handler/mailto;x-scheme-handler/webcal;" # bug #416393
# shellcheck disable=SC1117
make_desktop_entry \
chromium-browser \
"Chromium" \
chromium-browser \
"Network;WebBrowser" \
"MimeType=${mime_types}\nStartupWMClass=chromium-browser"
sed -e "/^Exec/s/$/ %U/" -i "${ED%/}"/usr/share/applications/*.desktop || die
# Install GNOME default application entry (bug #303100)
insinto /usr/share/gnome-control-center/default-apps
doins "${FILESDIR}"/chromium-browser.xml
readme.gentoo_create_doc
}
pkg_preinst() {
gnome2_icon_savelist
}
pkg_postrm() {
gnome2_icon_cache_update
xdg_desktop_database_update
}
pkg_postinst() {
gnome2_icon_cache_update
xdg_desktop_database_update
readme.gentoo_print_elog
} |
Last edited by maolang on Sat Oct 20, 2018 1:09 am; edited 3 times in total |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Sat Oct 20, 2018 12:48 am Post subject: |
|
|
in files folder of the ebuild
files/chromium-browser.xml
| Code: | <default-apps>
<script/>
<web-browsers>
<web-browser>
<name>Chromium</name>
<executable>chromium-browser</executable>
<command>chromium-browser %s</command>
<icon-name>chromium-browser</icon-name>
<run-in-terminal>false</run-in-terminal>
</web-browser>
</web-browsers>
</default-apps> |
files/chromium-launcher-r3.sh
| Code: | #!/bin/bash
# Allow the user to override command-line flags, bug #357629.
# This is based on Debian's chromium-browser package, and is intended
# to be consistent with Debian.
for f in /etc/chromium/*; do
[[ -f ${f} ]] && source "${f}"
done
# Prefer user defined CHROMIUM_USER_FLAGS (from env) over system
# default CHROMIUM_FLAGS (from /etc/chromium/default).
CHROMIUM_FLAGS=${CHROMIUM_USER_FLAGS:-"$CHROMIUM_FLAGS"}
# Let the wrapped binary know that it has been run through the wrapper
export CHROME_WRAPPER=$(readlink -f "$0")
PROGDIR=${CHROME_WRAPPER%/*}
case ":$PATH:" in
*:$PROGDIR:*)
# $PATH already contains $PROGDIR
;;
*)
# Append $PROGDIR to $PATH
export PATH="$PATH:$PROGDIR"
;;
esac
if [[ ${EUID} == 0 && -O ${XDG_CONFIG_HOME:-${HOME}} ]]; then
# Running as root with HOME owned by root.
# Pass --user-data-dir to work around upstream failsafe.
CHROMIUM_FLAGS="--user-data-dir=${XDG_CONFIG_HOME:-${HOME}/.config}/chromium
${CHROMIUM_FLAGS}"
fi
# Set the .desktop file name
export CHROME_DESKTOP="chromium-browser-chromium.desktop"
exec -a "chromium-browser" "$PROGDIR/chrome" --extra-plugin-dir=/usr/lib/nsbrowser/plugins ${CHROMIUM_FLAGS} "$@" |
files/chromium.default
| Code: | # Default settings for chromium. This file is sourced by /bin/bash from
# the chromium launcher.
# Options to pass to chromium.
#CHROMIUM_FLAGS="" |
Last edited by maolang on Sat Oct 20, 2018 1:03 am; edited 1 time in total |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Sat Oct 20, 2018 12:52 am Post subject: |
|
|
This pulls the latest available, built zip file
what would be nice is to choose a specific version (stable, beta, unstable)
If its possible otherwise this is simply a master -9999 version which i am ok with so far as it works flawlessly |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Sat Oct 20, 2018 12:54 am Post subject: |
|
|
| as of now, this pulls in the v. 72.0.3586.0 (Development Build ) (64 bits) |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Sat Oct 20, 2018 12:59 am Post subject: |
|
|
| Quote: | | So switch to a better browser, that isn't constantly broken? |
The browser itself is not the issue, its building it which is...
| Quote: | | Since you believe this is generally useful, perhaps you could share your work so that it is generally available to other people who want this? |
Added above the modified ebuild + the files folder content |
|
| Back to top |
|
|
maolang
n00b
Joined: 14 Sep 2018
Posts: 22
|
| Posted: Sat Oct 20, 2018 1:01 am Post subject: |
|
|
| All those were slightly modified from existing ebuild except the files/* which are as they were |
|
| Back to top |
|
|
Muso
Veteran
Joined: 22 Oct 2002
Posts: 1052
Location: The Holy city of Honolulu
|
| Posted: Sat Oct 20, 2018 2:12 am Post subject: |
|
|
| maolang wrote: | | All those were slightly modified from existing ebuild except the files/* which are as they were |
Welcome to Gentoo 
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop! |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21631
|
| Posted: Sat Oct 20, 2018 3:43 am Post subject: |
|
|
| maolang wrote: | | Code: | | SRC_URI="https://download-chromium.appspot.com/dl/Linux_x64?type=snapshots -> chromium-browser.zip" |
|
This is wrong, since the URL changes meaning as new snapshots are posted. SRC_URI should always refer to a download that will not change. You could resolve the redirect and save the versioned URL instead.
Also, since the download only works on amd64, consider wrapping the SRC_URI in amd64? ( ) so that other platforms download nothing. | maolang wrote: | | Code: | src_unpack() {
default
} |
|
default is the default implementation. You can remove src_unpack if there is nothing else to do here.
| maolang wrote: | | The browser itself is not the issue, |
The last time I used Chromium, the browser was quite an issue.  Extension support was terrible. |
|
| Back to top |
|
|
Cuong Nguyen
Apprentice
Joined: 18 Jan 2018
Posts: 152
|
| Posted: Sat Oct 20, 2018 9:29 am Post subject: |
|
|
I've just compiled the latest stable chromium-70.0.3538.67 with clang-7 llvm-7, ccache enabled. It took about 2 hr 30 mins on a box with dual Intel(R) Xeon(R) CPU X5570 @ 2.93GHz total of 16 threads, 32GB RAM. I located 30GB RAM as tmpfs for /var/tmp/portage and 6GB RAM as tmpfs for /var/tmp/ccache.
here is my llvm-clang.conf
| Code: |
CC="clang"
CXX="clang++"
LD="lld"
AR="llvm-ar"
NM="llvm-nm"
RANLIB="llvm-ranlib"
|
I've put www-client/chromium with 2 dependencies in package.env
| Code: |
www-client/chromium llvm-clang.conf
dev-libs/re2 llvm-clang.conf
app-text/hunspel llvm-clang.conf
|
USE-flags jumbo-build and custom-cflags also enabled with package.use
| Code: |
www-client/chromium custom-cflags jumbo-build
|
I havent tested the compiled binary yet. |
|
| Back to top |
|
|
|
Portage & Programming
