Bug 118520 – app-emacs/ecf: Emacs Configuration Framework (new ebuild)

• Status: RESOLVED WONTFIX
• Product: Gentoo Linux

[Description Dmitry S. Kulyabov 2006-01-10 05:06:57 UTC]

Package for emacs configuration

[Comment 1 Dmitry S. Kulyabov 2006-01-10 05:08:06 UTC]

Created attachment 76725 [details]
eclass/elisp-common.eclass

[Comment 2 Dmitry S. Kulyabov 2006-01-10 05:08:21 UTC]

Created attachment 76726 [details]
eclass/elisp.eclass

[Comment 3 Dmitry S. Kulyabov 2006-01-10 05:08:57 UTC]

Created attachment 76727 [details]
app-emacs/ecf-0.0.4.ebuild

[Comment 4 Dmitry S. Kulyabov 2006-01-10 05:09:40 UTC]

Created attachment 76728 [details]
app-emacs/tiny-tools-2005.1101.ebuild

[Comment 5 Ulrich Müller 2007-04-28 07:51:40 UTC]

Hi, I see the following issues:
- What will happen if the user changes the ecf USE flag? SITELISP will then be
  redefined and packages installed in the old directory will not found anymore.
- "addpredict" in an ebuild should be a last resort; in an eclass it is even
  worse. Can this be fixed?
- The USE variable should not be assigned by an ebuild.
- Why doesn't tiny-tools inherit elisp.eclass?

In general, this looks very invasive since it will affect all installed elisp packages, so we need a good reason to include it in Portage.

Can you elaborate what would be its advantages, as compared to the way Gentoo is handling things now?

[Comment 6 Ulrich Müller 2007-07-11 14:53:36 UTC]

No answer here, therefore closing.

Feel free to reopen if the points of comment #5 are addressed.