[Pkg-ime-devel] [ibus] about ibus input engine packaging.
aron at debian.org
Fri Jun 7 15:33:52 UTC 2013
On Fri, Jun 7, 2013 at 11:28 PM, Ma Xiaojun <damage3025 at gmail.com> wrote:
> On Fri, Jun 7, 2013 at 10:57 PM, Aron Xu <aron at debian.org> wrote:
>> Guess no, they are bugs which should not be covered by something like a policy.
> Where are the bugs?
>> I prefer filing bugs against all these packages. There is no concrete
>> way to handle the situation other than this, even though ibus-setup
>> can be modified to fallback to search old paths.
> The whole problem is created by current Debian's packaged directory
> structure for ibus-* not following the upstream's recommendation. If
> upstream's recommendation contradicts Debian's policy, we need to
> figure out a solution rather than leave things broken.
There isn't anything that upstream "recommended", everything is in
ibus's configuration script. Wherever the $libexecdir is set to,
ibus-setup is going to find plugins from that path. It's advisable
that upstream provide a solution for the case of real multi-arch
support, not only for what Fedora has (multilib).
More information about the Pkg-ime-devel