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 18:41:07 +0800 (CST)	[thread overview]
Message-ID: <6e5a32a2.24cb.177e313e316.Coremail.tumashu@163.com> (raw)
In-Reply-To: <83wnutom28.fsf@gnu.org>













At 2021-02-27 18:13:35, "Eli Zaretskii" <eliz@gnu.org> wrote:

>> Date: Sat, 27 Feb 2021 16:54:02 +0800 (CST)
>> From: tumashu  <tumashu@163.com>
>> Cc: "Stefan Monnier" <monnier@iro.umontreal.ca>, 
>> 	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
>> 
>> pyim core depend async, which is a GNU elpa package, and 
>> hard remove this depend.
>
>I see.
>
>> for the emacs-async reason, maybe pyim can not move to emacs.git,
>> maybe Gnu elpa is better place.
>
>I guess so.  Too bad.

maybe we should wait a sync package into emacs.git :-)

>
>> >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.
>
>This part is a problem even if pyim is only on ELPA.

This is not a big issue, without a Melpa package "pyim-basedict",  pyim can work properly,
pyim-basedict just let pyim more powful. 

as for pyim-basedict, it deriver from  libpinyin, libpinyin license is Apache 2.0

I do not know hao to deal with it,   put pyim-basedict to NonGNU elpa ?

>
>Thanks.

  reply	other threads:[~2021-02-27 10:41 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
2021-02-27 10:13                     ` Eli Zaretskii
2021-02-27 10:41                       ` tumashu [this message]
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=6e5a32a2.24cb.177e313e316.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).