Summary: | app-i18n/mozc-1.10.1390.102 - unused dev-libs/protobuf dependency? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jack Chen <speed.up08311990> |
Component: | Current packages | Assignee: | CJK Team <cjk> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jack Chen
2013-05-26 01:49:07 UTC
As per bug #251464 using the internal version is contrary to current QA policy. (In reply to Jeroen Roovers from comment #1) > As per bug #251464 using the internal version is contrary to current QA > policy. Oops, I didn't know that. Thank you for pointing it out. I'll keep in mind that I should avoid using internal library. However, the change was done according to this upstream bug: https://code.google.com/p/mozc/issues/detail?id=14 And this upstream revision: https://code.google.com/p/mozc/source/detail?r=96 (see also Gentoo bug #407581) They switched from linking shared protobuf to linking static protobuf by default in that version, so I followed that change. It seems that linking to shared protobuf library causes some issue in mozc, but I haven't encountered one personally when mozc was still using shared protobuf by default (I'm using mozc with ibus). The example given in the bug is related to uim-mozc. I can't find uim-mozc support in current mozc ebuild. If uim-mozc gets supported in the future, this issue may appear. I'd like to know how such confliction (between QA policy and upstream default) should be solved. I see there's bug 478094 which is fixed now. Should I close this one also? *** This bug has been marked as a duplicate of bug 478094 *** |