Bug 235442 - [Tracker] elisp-common.eclass: deprecate elisp-comp()
Bug#: 235442 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: All Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: emacs@gentoo.org Reported By: ulm@gentoo.org
Component: Eclasses and Profiles
URL: 
Summary: [Tracker] elisp-common.eclass: deprecate elisp-comp()
Keywords:  InCVS, Tracker
Status Whiteboard: 
Opened: 2008-08-22 11:05 0000
Description:   Opened: 2008-08-22 11:05 0000 
We don't need two separate byte-compile functions. A slightly updated
elisp-compile can be used in almost all cases, and the few (if any) ebuilds
could use their own custom code.

Use this bug as a tracker for ebuild still calling elisp-comp.

------- Comment #1 From Ulrich Müller 2008-08-22 11:08:24 0000 ------- 
Created an attachment (id=163544) [details]
Changes for elisp-common.eclass

This is already in the Emacs overlay for testing.

------- Comment #2 From Ulrich Müller 2008-08-23 11:23:31 0000 ------- 
(In reply to comment #0)
> [...] the few (if any) ebuilds could use their own custom code.

The few *remaining* ebuilds (i.e. that can't use elisp-compile) could use their
own custom code.

------- Comment #3 From Ulrich Müller 2008-08-27 07:06:24 0000 ------- 
Packages in category app-emacs that are still using elisp-comp (not filing
separate bugs for them):

   aspectj4emacs
   cc-mode
   delicious
   distel
   easypg
   emacs-jabber
   emacs-wget
   emacs-wiki
   fff
   gnuserv
   http-emacs
   icicles
   matlab
   mldonkey
   ocaml-mode
   python-mode
   ruby-mode
   slime
   sumibi
   tdtd
   tnt
   tuareg-mode
   view-process
   yatex

------- Comment #4 From Ulrich Müller 2008-08-28 09:16:36 0000 ------- 
(In reply to comment #3)
> Packages in category app-emacs that are still using elisp-comp (not filing
> separate bugs for them):
> 
>    aspectj4emacs
>    cc-mode
>    delicious
>    distel
>    easypg
>    emacs-jabber
>    emacs-wget
>    emacs-wiki
>    fff
>    gnuserv
>    http-emacs
>    icicles
>    matlab
>    mldonkey
>    ocaml-mode
>    python-mode
>    ruby-mode
>    slime
>    sumibi
>    tdtd
>    tnt
>    tuareg-mode
>    view-process

All done.

>    yatex

This was a false positive.


(In reply to comment #2)
> The few *remaining* ebuilds (i.e. that can't use elisp-compile) could use
> their own custom code.

It turns out that there is none, all can use the new elisp-compile.