Re-evaluate Linux Chrome package dependencies |
||
Issue descriptionWhen we first started packaging Chrome on Linux, we hoped LSB can serve as a foundation such that Chrome only needed to depend on LSB, plus a few more specific things aren't part of LSB (yet). This way, Chrome would worry less about differences between distros. As long as a given Linux install meet LSB requirements, then it mostly satisfies Chrome's dependencies. Some RPM-based distro users were never happy with this. (See bug 133327 ) Furthermore, Debian eventually dropped LSB support. [1] i.e. Debian 9 no longer has a lsb package and only retains lsb-based and lsb-release. As we pull back from depending on LSB in r474078 and r490728, we should take a moment and check our packaging dependencies to make sure it is complete. Otherwise, users can potentially succeed in installing a Chrome package, but not be able to actually run it. [1] https://lwn.net/Articles/658809/
,
Oct 3 2017
Hopefully our list of deps is complete now (besides the liberation-fonts dep on RPM which is left as a TODO0
,
Oct 4 2017
FYI - I requested the liberation-fonts package to be added to RHEL - https://bugzilla.redhat.com/show_bug.cgi?id=1482760 (I think that RHEL was the only RPM based distro missing that package).
,
Oct 4 2017
re: comment 3 - Thanks! I'll keep an eye on that. |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Oct 2 2017