[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [elpa] externals/pyim 1e14e7c: V3.1
From: |
Eli Zaretskii |
Subject: |
Re: [elpa] externals/pyim 1e14e7c: V3.1 |
Date: |
Sat, 27 Feb 2021 12:56:24 +0200 |
> Date: Sat, 27 Feb 2021 18:41:07 +0800 (CST)
> From: tumashu <tumashu@163.com>
> Cc: "Stefan Monnier" <monnier@iro.umontreal.ca>,
> "emacs-devel@gnu.org" <emacs-devel@gnu.org>
>
> >> 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 :-)
I think there was talk about doing that. I don't know what is the
status of that. John, any comments?
> >> >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 ?
Yes, having that in non-GNU ELPA would be a good step.
- Re: [elpa] externals/pyim 1e14e7c: V3.1, (continued)
- Re:Re: [elpa] externals/pyim 1e14e7c: V3.1, tumashu, 2021/02/25
- Re:Re: [elpa] externals/pyim 1e14e7c: V3.1, tumashu, 2021/02/26
- Re: [elpa] externals/pyim 1e14e7c: V3.1, Eli Zaretskii, 2021/02/26
- Re:Re: [elpa] externals/pyim 1e14e7c: V3.1, tumashu, 2021/02/27
- Re: [elpa] externals/pyim 1e14e7c: V3.1, Eli Zaretskii, 2021/02/27
- Re:Re: [elpa] externals/pyim 1e14e7c: V3.1, tumashu, 2021/02/27
- Re: [elpa] externals/pyim 1e14e7c: V3.1,
Eli Zaretskii <=
- Re:Re:Re: [elpa] externals/pyim 1e14e7c: V3.1, tumashu, 2021/02/27
- Re: [elpa] externals/pyim 1e14e7c: V3.1, Stefan Monnier, 2021/02/27