I am unfortunately neither a programmer myself.
Though as far as I have learnt by contacting the authors of the patches it wouldn't be you to maintain the npapi (don't know why I always tend to write napi lol) patch but the guys from Pipelight, at least as long as the npapi feature is possible (please see, https://answers.launchpad.net/pipelight/+question/250336 ).
Therefore you would actually "just" have to care about the no-SSE2 aspect if I understand the situation the right way.
Hopefully this sheds some light on the doubts/concerns that you have expressed.
Search Criteria
Package Details: chromium-no-sse2 36.0.1985.143-1
Package Actions
Package Base: | chromium-no-sse2 |
---|---|
Description: | The open-source project behind Google Chrome, without an sse2 dependency |
Upstream URL: | https://github.com/graysky2/chromium-no-sse2-patch |
Category: | network |
Licenses: | |
Conflicts: | |
Provides: | |
Submitter: | graysky |
Maintainer: | graysky |
Last Packager: | graysky |
Votes: | 3 |
First Submitted: | 2014-05-24 12:05 |
Last Updated: | 2014-08-15 07:30 |
Dependencies (34)
- alsa-lib
- bzip2
- clang (make)
- dbus
- desktop-file-utils
- elfutils (make)
- flac
- gnome-keyring (optional) – for storing passwords in GNOME keyring
- gperf (make)
- gtk2
- harfbuzz
- hicolor-icon-theme
- kdebase-kdialog (optional) – needed for file dialogs in KDE
- kdeutils-kwalletmanager (optional) – for storing passwords in KWallet
- libevent
- libexif
- libgcrypt
- libgnome-keyring (make)
- libgnome-keyring (optional) – for storing passwords in GNOME keyring
- libpulse
- libxss
- mesa (make)
- ninja (make)
- nss
- pciutils
- perl (make)
- python2 (make)
- snappy
- speech-dispatcher
- subversion (make)
- systemd
- ttf-font
- xdg-utils
- yasm (make)
Required by (0)
Sources
- chromium-nacl-bootstrap-cflags.patch
- chromium.default
- chromium.desktop
- chromium.sh
- https://commondatastorage.googleapis.com/chromium-browser-official/chromium-36.0.1985.143.tar.xz
- https://raw.githubusercontent.com/graysky2/chromium-no-sse2-patch/master/undo_removing_sse2_for_v36.patch
Latest Comments
Comment by rcct
Comment by graysky
I am not a programmer so maintaining this patch might be difficult if upstream code significant deviates from it in the current state. I and others cannot maintain the chromium-scroll-pixels package for v35 due to a major re-write upstream. I don't want this package to suffer the same fate if the code in the patches you are requesting becomes unmanageable as well. If you want to, you can modify the PKGBUILD to include my patch here + whatever you want, but I cannot.
Comment by rcct
I forgot to add that if older hardware is part of the scope providing a fully functional, or at least as functional as possible, chromium (including flash which already hit the users with the 'SSE2 hammer' quite some time back) could be part of it.
In the end I just ask if it is possible for you to consider including it.
Comment by rcct
The issue refers to +35 version completely dropping NAPI support, affecting among others the Pipelight program, see
https://wiki.archlinux.org/index.php/Pipelight#Pipelight_stopped_working_after_upgrade_of_chromium_.28version_35.2B.29
I am aware that the scope may be or actually is very narrow that is why I ask if there is room, as said in an additional version, for that issue too.
Comment by graysky
No idea what that NAPI issue is... this package is very narrow in its scope: provide chromium to older hardware.
Comment by rcct
First of all, thanks for this no-SSE2 package.
Besides handling, so to speak, the SSE2 issue do you plan to address the lack of NAPI support in the +35 versions too? F.e. in an additional version to this one for users to be able to choose which to use.
Comment by graysky
For those not wanting to compile this build this package, I am hosting a pre-compiled version on repo-ck, and plan to keep it updated since I use chromium-no-sse2 on several of my Athlon XP machines that are still alive, see: https://wiki.archlinux.org/index.php/Repo-ck#Miscellaneous_packages
Comment by graysky
For those not wanting to compile this build this package, I am hosting a pre-compiled version on repo-ck, see: https://wiki.archlinux.org/index.php/Repo-ck#Miscellaneous_packages