This idea is stolen from Arch Linux, but still nice: <http://code.google.com/p/cj-overlay/source/browse/www-plugins/google-chrome-libpdf/google-chrome-libpdf-16.0.912.75_p116452.ebuild> Opinions? I can maintain it.
[Adding link to related bug, closed WONTFIX] I was maintaining a similar package "chromium-pdf" in my overlay for a bit before I became a dev, but I stopped updating it out of laziness. Personally, I just have symlinks from /usr/lib64/chromium-browser{,-live}/libpdf.so to /opt/google/chrome/libpdf.so. This picks up the copy that is installed by www-client/google-chrome. If you want to maintain it, feel free to adapt my google-chrome version bump script. http://dev.gentoo.org/~floppym/chrome-bump
(In reply to comment #1) > [Adding link to related bug, closed WONTFIX] > > I was maintaining a similar package "chromium-pdf" in my overlay for a bit > before I became a dev, but I stopped updating it out of laziness. > > Personally, I just have symlinks from > /usr/lib64/chromium-browser{,-live}/libpdf.so to /opt/google/chrome/libpdf.so. > This picks up the copy that is installed by www-client/google-chrome. > > If you want to maintain it, feel free to adapt my google-chrome version bump > script. > > http://dev.gentoo.org/~floppym/chrome-bump Hmm, do one need to have exactly same version of libpdf as chromium?
(In reply to comment #2) Not necessarily. We really have no way of knowing when Google is going to make an incompatible change, however.
(In reply to comment #3) > (In reply to comment #2) > > Not necessarily. We really have no way of knowing when Google is going to make > an incompatible change, however. True. So I will keep it in my overlay for now. Thanks.
