Package Details: chromium-dev 126.0.6423.2-1

Git Clone URL: https://aur.archlinux.org/chromium-dev.git (read-only, click to copy)
Package Base: chromium-dev
Description: The open-source project behind Google Chrome (Dev Channel)
Upstream URL: http://www.chromium.org
Keywords: browser web
Licenses: BSD
Submitter: None
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 160
Popularity: 0.019686
First Submitted: 2010-05-17 09:04 (UTC)
Last Updated: 2024-04-21 19:18 (UTC)

Required by (0)

Sources (13)

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 152 Next › Last »

<deleted-account> commented on 2017-05-13 18:48 (UTC)

If you find an error saying /usr/lib/chromium-dev/chromium-dev: error while loading shared libraries: libwebp.so.6: cannot open shared object file: No such file or directory you can fix it like this sudo ln -s /usr/lib64/libwebp.so.7 /usr/lib64/libwebp.so.6

<deleted-account> commented on 2017-05-12 03:59 (UTC)

Nice job on the very quick update :)

axfelix commented on 2017-05-08 17:37 (UTC)

Does this build not contain the new support for native notifications on Linux? Is that somehow only in Chrome rather than Chromium?

sl1pkn07 commented on 2017-05-03 13:57 (UTC)

@M4P9be3w0u done

M4P9be3w0u commented on 2017-05-02 22:52 (UTC)

I had to modify to the file "vaapi_patch_r0.patch" to compile version 60.0.3080.5-1 with vaapi enabled. Find the patch file that worked for me here: https://pastebin.com/qMH50eKS . (Disclaimer: not sure if this is the right place to poste this. May not work for eveyone.)

LordAro commented on 2017-04-18 09:56 (UTC)

oh indeed, that's how i built the package in the end. the question is whether the PKGBUILD *should* be able to handle being called in separate steps. Should probably take this to a mailing list...

sl1pkn07 commented on 2017-04-17 16:53 (UTC) (edited on 2017-04-17 16:57 (UTC) by sl1pkn07)

try with plain makepkg ;) (without options)

LordAro commented on 2017-04-17 16:43 (UTC)

I'm not convinced it is pacaur's bug though - it's this PKGBUILD that failed to build with makepkg -o && makepkg -es . I'll be quite happy to raise a bug report with pacaur if you can show that your PKGBUILD is doing it "correctly" (with documentation or whatever)

sl1pkn07 commented on 2017-04-16 12:33 (UTC)

open bug in pacaur. nothing to do in the pkgbuild

LordAro commented on 2017-04-16 10:28 (UTC)

@sl1pkn07 ah, found the issue. pacaur calls makepkg -o followed by makepkg -es Since your PKGBUILD only sets the $PATH in the prepare() function, the changes don't get added to the build() and other functions. Seems like the PATH change should be added either more globally (can you do that?) or to the other functions as needed

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 152 Next › Last »