[Pkg-ime-devel] Bug#746978: Bug#746978: Bug#746978: ibus-cangjie: Please set libexecdir as other ibus packages
Hi,
On Mon, Jun 09, 2014 at 12:38:07AM +0800, ChangZhuo Chen wrote:
> On Sat, Jun 07, 2014 at 12:59:14AM +0900, Osamu Aoki wrote:
> > I disagree.
> >
> > This is Debian @packaging problem. See other ibus-* packages.
>
> I see, so putting ibus-engine-* into /usr/lib/ibus is debian specific,
> right?
If you call Debian use of /usr/lib for GNU/RedHat style /usr/libexec as
"Debian specific", YES.
The rationale of /usr/lib/ibus/ibus-engine-cangjie over your
/usr/lib/ibus-cangjie/ibus-engine-cangjie is more of consistency
question as a part of ibus package.
As I checked, for this package, since cangjie.xml has
<exec>/usr/lib/ibus-cangjie/ibus-engine-cangjie --ibus cangjie</exec>
it may function as this. (Some ibus tool search /usr/lib/ibus as I
recall. It may not be true any more.)
But when I get bug report on ibus, I can not detect installation of
ibus-engine-cangjie as easy as others if you chose to use such path.
I summarized these in https://wiki.debian.org/Teams/IMEPackagingTeam/ibus
> Currently upstream hardcode the libexecdir in Makefile.am due to
> maintainability [0]. So is there any reason why debian put ibus-engine-*
> into /usr/lib/ibus so that we can persuade upstream to support
> --libexecdir?
No no no no we do not care about it. We have configure script to adopt
package to Debian. That is what Debian packaging is about.
Upstream should not make strange thing here and he is doing the right
thing like addressing Debian specific multi-arch path. If you make your
package multi-arch as other packages, you need to set --libexecdir
anyway.
Osamu
PS: We even wish to use the autoreconf -ivf strategy to build package
from configure.ac for better arch support. See many bugs filed for
supporting AArch64 which is fixed by autoreconf .
Reply to: