unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tumashu  <tumashu@163.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re:Re: [elpa] externals/pyim 1e14e7c: V3.1
Date: Sat, 27 Feb 2021 16:54:02 +0800 (CST)	[thread overview]
Message-ID: <71fd8f5a.1f8f.177e2b1da8d.Coremail.tumashu@163.com> (raw)
In-Reply-To: <83im6fqnom.fsf@gnu.org>

At 2021-02-26 15:43:21, "Eli Zaretskii" <eliz@gnu.org> wrote:
>> Date: Fri, 26 Feb 2021 13:26:09 +0800 (CST)
>> From: tumashu  <tumashu@163.com>
>> Cc: "Stefan Monnier" <monnier@iro.umontreal.ca>, 
>> 	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
>> 
>> I think we have other problem to put pyim to emacs.git.
>> 1. pyim require xr and rx, and  xr is a GNU elpa package, 
>> 2. pyim support liberime, which is a melpa package.
>
>That's unfortunate.  Can these dependencies be removed in some way?
>
>Also, are these dependencies needed always, or just for some features

pyim core depend async, which is a GNU elpa package, and 
hard remove this depend.

a very useful feature (use pinyin search Chinese ) require xr

as liberime, pyim can work well with rime input method with the help of liberime. 

>of the pyim input method.  IOW, if the user only wants to use the
>input method, i.e. type "C-u C-\ pyim RET" and type the characters,
>does such a user need these dependencies?  If not, perhaps the
>dependencies could be made optional if not removed.

for the emacs-async reason, maybe pyim can not move to emacs.git,
maybe Gnu elpa is better place.

>
>And I think the dependency on MELPA is the most worrisome, as we try
>not to encourage users to install packages from there, let alone force
>them do it.






  reply	other threads:[~2021-02-27  8:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210224023820.26915.3177@vcs0.savannah.gnu.org>
     [not found] ` <20210224023821.4146320536@vcs0.savannah.gnu.org>
2021-02-24  4:41   ` [elpa] externals/pyim 1e14e7c: V3.1 Stefan Monnier
2021-02-24  5:37     ` tumashu
2021-02-24 13:52       ` Stefan Monnier
2021-02-24 16:41         ` Eli Zaretskii
2021-02-25  2:25           ` tumashu
2021-02-25 14:25             ` Eli Zaretskii
2021-02-25 14:30               ` Stefan Monnier
2021-02-25 15:10                 ` Eli Zaretskii
2021-02-25 15:35                   ` Stefan Monnier
2021-02-25 15:38                     ` Eli Zaretskii
2021-02-26  0:58               ` tumashu
2021-02-26  5:26               ` tumashu
2021-02-26  7:43                 ` Eli Zaretskii
2021-02-27  8:54                   ` tumashu [this message]
2021-02-27 10:13                     ` Eli Zaretskii
2021-02-27 10:41                       ` tumashu
2021-02-27 10:56                         ` Eli Zaretskii
2021-02-27 10:59                         ` tumashu
2021-02-27 14:46                   ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=71fd8f5a.1f8f.177e2b1da8d.Coremail.tumashu@163.com \
    --to=tumashu@163.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).