[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#955236: ibus-libthai: Migrate from /usr/lib/ibus to /usr/libexec



Package: ibus-libthai
Version: 0.1.4-5
Severity: wishlist


Hello,

ibus-libthai uses --libexec-dir=/usr/lib/ibus configure flag. But it is
not needed anymore. Please remove the --libexec-dir flag in the next 
uploads.

ibus-libthai has setup in /usr/lib/ibus but it was specified in the <setup> in
the XML so you don't have to change other things.


Details:

ibus used /usr/lib/ibus as "libexec" dir for FHS 2.x compliance.
And all the ibus engine packages also used the same libexec dir
/usr/lib/ibus, because ibus-setup searched ibus-setup-NAME in libexec 
dir as fallback.

But FHS 3.0 allows using /usr/libexec, so the newer ibus 1.5.22-2
just uses /usr/libexec. ibus-setup provides compatibility with the old
fallback setup path /usr/lib/ibus/ibus-setup-NAME. When ibus-setup 
uses such a fallback, it will display a warning like this:

  Warning: Using old FHS 2.x path /usr/lib/ibus/ibus-setup-NAME

This FHS 2.x compatibility is to be removed after some time.

If your ibus-NAME package have explicit <setup> in 
your /usr/share/ibus/NAME.xml, you don't have to worry and just remove 
--libexec-dir=/usr/lib/ibus flag in the next uploads.

If your package does not have <setup> in /usr/share/ibus/<NAME>.xml,
it is encouraged to patch your package to have <setup> in the XML. 
Then it will work with older versions of ibus package. For example:

https://salsa.debian.org/input-method-team/ibus-hangul/blob/master/debian/patches/specify-setup-in-ibus-component.patch

Please don't forget to upstream the changes.

Without <setup> or --libexec-dir flag, /usr/libexec/ibus-setup-NAME will 
work only with the newer versions of ibus. If it's too difficult to patch 
and you decided not to patch, don't forget to add the versioned dependency 
"ibus (>= 1.5.22-2)" to Depends.


Thanks,


Reply to: