Okay, I get what you mean.
Search Criteria
Package Details: ibus-input-support 20250211-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/manjaro-asian-input-support.git (read-only, click to copy) |
---|---|
Package Base: | manjaro-asian-input-support |
Description: | Asian input support from Manjaro for ibus |
Upstream URL: | https://gitlab.manjaro.org/packages/extra/manjaro-asian-input-support |
Licenses: | GPL-3.0-or-later |
Conflicts: | manjaro-asian-input-support-fcitx, manjaro-asian-input-support-fcitx5 |
Provides: | manjaro-asian-input-support-ibus |
Submitter: | SamLukeYes |
Maintainer: | phoepsilonix |
Last Packager: | phoepsilonix |
Votes: | 3 |
Popularity: | 0.157668 |
First Submitted: | 2020-06-30 09:37 (UTC) |
Last Updated: | 2025-04-03 06:29 (UTC) |
Dependencies (5)
- ibus (ibus-gitAUR)
- ibus-anthy (optional) – 日本語 | Japanese
- ibus-hangul (ibus-hangul-3beolAUR, ibus-hangul-gitAUR) (optional) – 한국어 | Korean
- ibus-libpinyin (optional) – 中文 | Chinese
- ibus-unikey (optional) – Tiếng Việt | Vietnamese
Required by (0)
Sources (6)
willvar commented on 2025-04-04 08:04 (UTC)
phoepsilonix commented on 2025-04-04 07:55 (UTC)
@willvar
The version and release number have not been changed as there are no functional changes.
I would appreciate it if you could reinstall the software and downgrade the version number or uninstall and re-install.
willvar commented on 2025-04-04 06:48 (UTC)
Oh I see your commit but the .SRCINFO is not updated so I didn't get any update.
phoepsilonix commented on 2025-04-03 06:32 (UTC) (edited on 2025-04-03 06:42 (UTC) by phoepsilonix)
@willvar
As you say, it would certainly be annoying.
I have now fixed the version.
Since the AUR is built by the users themselves, it would be more appropriate to fix the version rather than leave the upstream settings. Your point is well taken.
Thank you for your report.
willvar commented on 2025-04-03 06:18 (UTC)
Here I am again, with a question about the following PKGBUILD snippet:
pkgver() {
date +%Y%m%d
}
I’ve noticed that when I install fcitx5-input-support, the package version always matches the current date. However, during rolling updates, I often see messages like:
:: Searching databases for updates...
-> fcitx5-input-support: local (20250403-1) is newer than AUR (20250211-1)
The local version is always flagged as newer than the AUR version, this is a little bit annoying. Could you kindly clarify this? I’m curious about the reason behind it, thanks!
phoepsilonix commented on 2025-03-19 15:13 (UTC) (edited on 2025-03-21 07:06 (UTC) by phoepsilonix)
@MatrixC7
Fcitx5 has been updated and the problems I encountered earlier, caused by setting environment variables, may have improved. Nevertheless, the fact remains that Fcitx5 displays a message at startup in the KDE+Wayland environment, prompting the user to remove GTK_IM_MODULE and QT_IM_MODULE. You should therefore exchange your views with the developers and maintainers of Fcitx5 itself. If you think that my stance of following it is wrong, then you should create your own package and undertake to include support for those who use your package. That would be a practical solution.
It is not constructive to ignore my previous posts, specifically the cases where I have encountered trouble with setting environment variables, and to keep pointing out one-sidedly that my choices are wrong without also telling me what environment you are using. This is because even if You didn't encounter any problems in your environment, it is a fact that I did in my old environment.
As stated in the Fcitx5 startup message, it is recommended to use the Kwin VitrualKeyboard to start the Fcitx5 Wayland Launcher. That would still be the message from the developers. If you disagree with it, you should tell the Fcitx5 developers and maintainers.
You are asking me to do something different from the configuration recommended by the Fcitx5 developers, and I don't think it is a good decision for me to take you at your word. Therefore, I recommend that you create your own package and maintain it yourself. By doing so, the AUR can fulfil the purpose for which it exists.
phoepsilonix commented on 2025-03-19 14:06 (UTC)
@MatrixC7
This package is based on manjaro's configuration. manjaro's Kde environment has the kwin virtual keyboard enabled by default. fcitx5 also recommends running with the kwin virtual keyboard, as explained in the previous URL. It also displays a message recommending it. Since you do not describe your environment, I am assuming that you are using kde with wayland, but not with kwin virtual keyboard? In other words, you are using it in a way that is not recommended by fcitx5?
Your insistence that the old setup is fine ignores my previous posts. snap, flatpak, and aur are applications that are managed externally by the distribution, and the input method may not launch when using common applications in the repositories managed by the distribution, such as firefox. This is why the configuration has been changed. In other words, in wayland, you cannot use fcitx5, etc. for language input of multibyte characters in common applications with the old configuration. If your environment is different from mine and you prefer the old configuration, you should make a new aur package for yourself. That would be the best and easiest way to aur. I have installed and tried multiple environments and have come to the conclusion I have now. I am not a psychic, so, Since you do not describe your environment, I have no way of ascertaining why you are ignoring my previous posts and making such claims.
Pinned Comments
phoepsilonix commented on 2025-01-21 08:32 (UTC)
https://gitlab.manjaro.org/packages/extra/manjaro-asian-input-support/