[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gettext] Why not have po-mode.el on GNU ELPA?

From: Daiki Ueno
Subject: Re: [bug-gettext] Why not have po-mode.el on GNU ELPA?
Date: Tue, 28 Jul 2015 22:26:46 +0900
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

Jordon Biondo <address@hidden> writes:

> Compatibility hacks are not uncommon for emacs packages, but I can say
> I compiled it as a package on the latest development branch without
> any problems recently. So I don't see a big issue there even if there
> are a few warnings as long as it works correctly with the hacks.

I see the following:

  In toplevel form:
  po-compat.el:48:16:Warning: assignment to free variable `po-EMACS20'
  po-compat.el:48:29:Warning: assignment to free variable `po-XEMACS'
  In toplevel form:
  po-mode.el:81:16:Warning: assignment to free variable `po-EMACS20'
  po-mode.el:81:29:Warning: assignment to free variable `po-XEMACS'
  In end of data:
  po-compat.el:264:1:Warning: the following functions are not known to be
      defined: cp-supported-codepages, codepage-setup

I tried to suppress them without breaking compatibility, but soon
realized that it is not worth the effort.  What I am actually worried
about is that po-mode.el could diverge if the file were maintained
separately in gettext and in ELPA.

>     the authors would need to assign copyright for Emacs, as well as
>     for gettext.
> This is true, but if getting authors to assign copyright is a problem
> there are other ELPA repositories besides the official GNU one, Melpa
> being the most popular.

I personally would prefer GNU ELPA, since gettext is a GNU package, and
the GNU ELPA packages are digitally signed (I am not sure if MELPA has
the same capability).

> I will write to emacs-devel, and get their thoughts.


Daiki Ueno

reply via email to

[Prev in Thread] Current Thread [Next in Thread]