Github messages for voidlinux
 help / color / mirror / Atom feed
From: Gorggg <Gorggg@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] uim: disable non-utf-8 anthy backend
Date: Sun, 04 Apr 2021 21:49:36 +0200	[thread overview]
Message-ID: <20210404194936.9zSyor595GIqBwfRRJo0Q0rUfuSFNsEP-LzTZGk7b8U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29981@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]

There is an updated pull request by Gorggg against master on the void-packages repository

https://github.com/Gorggg/void-packages master
https://github.com/void-linux/void-packages/pull/29981

uim: disable non-utf-8 anthy backend
After the recent upgrade of anthy to 0.4 in [https://github.com/void-linux/void-packages/commit/700c49292eccc0cd96372e45027e2a929229e060](https://github.com/void-linux/void-packages/commit/700c49292eccc0cd96372e45027e2a929229e060), the anthy input method in uim will no longer work with the anthy available in the repository, instead requiring the anthy-utf8 input method to interface and convert kanji correctly. In order to prevent broken configurations, this change disables the build of the old anthy input method.

In order to avoid installing the new build of uim-anthy when the old anthy is present, I set uim-anthy to conflict with older versions of anthy that use EUC-JP instead of UTF-8. If there is a better way of ensuring this is not installed in a way that introduces incompatibility, I would very much like to know.

Thank you for reading this and for any reply.

<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/29981.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-29981.patch --]
[-- Type: text/x-diff, Size: 1450 bytes --]

From 0e361ecf35b5b2d22907273428dd61941cb33776 Mon Sep 17 00:00:00 2001
From: George Matsumura <gmmatsumura01@bvsd.org>
Date: Sat, 3 Apr 2021 03:22:39 -0600
Subject: [PATCH] uim: disable non-utf-8 anthy backend

The version of anthy (0.4) that is now in the repository will not
work correctly with uim's conventional anthy input method, failing
to convert kanji. It will only with the anthy-utf-8 input method,
which accounts for the substitution of the EUC-JP encoding with
UTF-8 in newer anthy versions. In order to prevent broken
configurations, this change disables the build of the old anthy
input method.
---
 srcpkgs/uim/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/uim/template b/srcpkgs/uim/template
index 12df0eddb067..df686e2a3acf 100644
--- a/srcpkgs/uim/template
+++ b/srcpkgs/uim/template
@@ -1,12 +1,12 @@
 # Template file for 'uim'
 pkgname=uim
 version=1.8.8
-revision=4
+revision=5
 build_style=gnu-configure
 build_helper=qmake
 configure_args="--enable-pref --enable-fep --with-gtk2 --with-gtk3
- --with-libgcroots=installed
- --with-qt5 --with-qt5-immodule --with-x --with-anthy-utf8 --with-skk"
+ --with-libgcroots=installed --with-qt5 --with-qt5-immodule --with-x
+ --with-anthy-utf8 --without-anthy --with-skk"
 hostmakedepends="pkg-config intltool qt5-host-tools qt5-qmake automake
  libtool gettext-devel"
 makedepends="gtk+-devel gtk+3-devel qt5-devel ncurses-devel anthy-devel

  parent reply	other threads:[~2021-04-04 19:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03 20:15 [PR PATCH] " Gorggg
2021-04-03 22:01 ` ericonr
2021-04-04 15:45 ` sgn
2021-04-04 19:47 ` Gorggg
2021-04-04 19:49 ` Gorggg [this message]
2021-04-04 19:50 ` Gorggg
2021-04-05  0:55 ` sgn
2021-04-05  0:55 ` sgn
2021-04-05  0:56 ` sgn
2021-04-05  2:04 ` Gorggg
2021-04-05  2:04 ` Gorggg
2021-04-05  2:05 ` Gorggg
2021-04-05  2:25 ` Gorggg
2021-04-06 12:23 ` sgn
2021-04-06 16:02 ` Gorggg
2021-04-07  0:15 ` sgn
2021-04-14 23:47 ` sgn
2021-04-15 14:39 ` [PR PATCH] [Closed]: " sgn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210404194936.9zSyor595GIqBwfRRJo0Q0rUfuSFNsEP-LzTZGk7b8U@z \
    --to=gorggg@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).