PackagingDrafts/Emacs-Dec2011

= Packaging of add-ons for GNU Emacs and XEmacs =

Purpose
The purpose of this document is to promote good practice in packaging add-ons for GNU Emacs and XEmacs, and to encourage the submission of more Emacs add-on packages to the package collection by providing easy to use spec file templates.

This document refers to packaging for Fedora 12 onwards. If you are packaging for an older release of Fedora, please see: Packaging:Emacs_Old

Important notes on these Guidelines
The guidelines in the following sections make extensive use of the macros defined in /etc/rpm/macros.emacs and /etc/rpm/macros.xemacs which are installed with the emacs-common and xemacs-common packages.

There are two distinct cases where consideration of these guidelines is required:


 * 1) This case refers to the situation where a package's principal purpose is to provide extra functionality for (X)Emacs, and the package serves no purpose without the presence of (X)Emacs. An example of this case is the VM mail reader, as packaged in emacs-vm. Below we refer to this as Case I.
 * 2) This case refers to the situation where a package's principal functionality does not require (X)Emacs, but the package also includes some auxiliary Elisp files to provide support for the package in (X)Emacs. Below we refer to this as Case II.

Case I

 * 1) Where an add-on package foo is for both GNU Emacs and XEmacs, the main package should be called emacs-common-foo. This main package should contain files common to both GNU Emacs and XEmacs such as documentation etc. Files specific to each of GNU Emacs and XEmacs should be placed in sub-packages called emacs-foo and xemacs-foo.
 * 2) Where a package is primarily an add-on for one flavour of (X)Emacs, the main package should be called emacs-foo or xemacs-foo.

Case II
Where a package's principal functionality does not require (X)Emacs, but the package also includes some auxiliary Elisp files to provide support for the package in (X)Emacs, these should be included in the main package which will need to Require the emacs-filesystem and/or xemacs-filesystem packages. More detail below.

Case I

 * 1) Files specific to GNU Emacs should be placed in a sub-package called emacs-foo. This should contain the elisp source, compiled elisp and any other files needed to use the package or sub-package with GNU Emacs.
 * 2) Files specific to XEmacs should be placed in a sub-package called xemacs-foo. This should contain the elisp source, compiled elisp and any other files needed to use the add-on package or sub-package with XEmacs.

Case II
The compiled elisp source and the elisp source files should be packaged as part of the main package, and not split out into separate packages.

File locations

 * 1) File locations for GNU Emacs add-on (sub-)packages:
 * 2) * All elisp and related files for the package should be installed in the directory.
 * 3) * If the package requires a startup file this should be called foo-init.el and be placed in.
 * 4) File locations for XEmacs add-on (sub-)packages:
 * 5) * All elisp files for package should be installed in the directory  (  translates to  )
 * 6) * All other files for the add-on package should be installed under the relevant sub-directories in   eg.   (  translates to  ).
 * 7) * If the package requires a startup file this should be called  and be placed in.

Case I

 * 1) Package Requires for GNU Emacs add-on (sub-)packages
 * 2) * Where relevant emacs-foo must have
 * 3) * emacs-foo must have
 * 4) Package Requires for XEmacs add-on (sub-)packages
 * 5) * Where relevant xemacs-foo must have
 * 6) * xemacs-foo must have

Case II

 * 1) If the package has auxillary files for use with GNU Emacs, the package must have
 * 2) If the package has auxillary files for use with XEmacs, the package must have

Package BuildRequires

 * 1) Package BuildRequires for GNU Emacs add-on packages:
 * 2) * In general it should suffice to have
 * 3) Package BuildRequires for XEmacs add-on packages:
 * 4) * In general it should suffice to have
 * 5) * It may be necessary to also add  in rare circumstances

Manual byte compilation
Usually package Elisp compilation is handled via a make file shipped with the package, but on some occasions it may be necessary to add commands to the %build section of the spec file to byte compile files. The following macros are provided to help with this:


 * For GNU Emacs byte compilation, use
 * For XEmacs byte compilation, use

It is a requirement that all Elisp files are byte compiled and packaged, unless there is a good reason not to, in which case this should be documented with a comment in the spec file. If you are packaging for both GNU Emacs and XEmacs, be sure to byte compile for both.

Use of BuildArch: noarch
If an add-on package requires only byte compilation of elisp then  should be used. This is highly unlikely to ever apply to Case II.

Template for a package for both GNU Emacs and XEmacs (Case I)
This spec-file template for the add-on package "foo" creates 3 packages:


 * 1) emacs-common-foo is the main package. This should contain files which are common to both the emacs-foo and xemacs-foo subpackages below. Examples of what this file would contain are the package documentation, the COPYING file, the CHANGELOG file etc.
 * 2) emacs-foo. This sub-package Requires emacs-common-foo and contains the files needed to run foo with Emacs only. This package contains both the compiled and source elisp files.
 * 3) xemacs-foo. This sub-package Requires emacs-common-foo and contains the files needed to run foo with Emacs only. This package contains both the compiled and source elisp files.

For convenience, there are two macros at the top of the file which you should customise to your package. You do not have to use the macros placed at the top of the file, but they help readability and make writing a spec file for a new package much quicker.

%global pkg foo %global pkgname Foo

Name:          emacs-common-%{pkg} Version: Release:       1%{?dist} Summary:

Group: License: URL: Source0:

BuildArch:	noarch BuildRequires: emacs BuildRequires: xemacs Requires:

%description %{pkgname} is an add-on package for GNU Emacs and XEmacs. It does wonderful things...

This package contains the files common to both the GNU Emacs and XEmacs %{pkgname} packages.

%package -n emacs-%{pkg} Summary:	Compiled elisp files to run %{pkgname} under GNU Emacs Group: Requires:	emacs(bin) >= %{_emacs_version} Requires:      emacs-common-%{pkg} = %{version}-%{release}

%description -n emacs-%{pkg} This package contains the byte compiled elisp packages to run %{pkgname} with GNU Emacs.

%package -n xemacs-%{pkg} Summary:	Compiled elisp files to run %{pkgname} under XEmacs Group: Requires:	xemacs(bin) >= %{_xemacs_version} Requires:      emacs-common-%{pkg} = %{version}-%{release}

%description -n xemacs-%{pkg} This package contains the byte compiled elisp packages to use %{pkgname} with XEmacs.

%prep %setup -q -n %{pkg}-%{version}

%build

%install

%post

%preun

%files %doc

%files -n emacs-%{pkg} %{_emacs_sitelispdir}/%{pkg} %{_emacs_sitestartdir/*.el

%files -n xemacs-%{pkg} %{_xemacs_sitelispdir}/%{pkg} %{_xemacs_sitestartdir}/*.el

%changelog

Template for a add-on package for GNU Emacs only (Case I)
This is a template for a package for GNU Emacs only. The main package is called emacs-foo and contains all files needed to run package foo with GNU Emacs. This includes both compiled and source elisp files.

%global pkg foo %global pkgname Foo

Name:          emacs-%{pkg} Version: Release:       1%{?dist} Summary:

Group: License: URL: Source0:

BuildArch:     noarch BuildRequires: emacs Requires:      emacs(bin) >= %{_emacs_version}

%description %{pkgname} is an add-on package for GNU Emacs. It does wonderful things...

%prep %setup -q -n %{pkg}-%{version}

%build

%install

%post

%preun

%files %doc %{_emacs_sitelispdir}/%{pkg} %{_emacs_sitestartdir}/*.el

%changelog

Template for a package which contains auxilliary GNU Emacs and XEmacs files (Case II)
This is a skeleton of a package which also includes support files for both GNU Emacs and XEmacs Name:          foo Version: Release:       1%{?dist} Summary:

Group: License: URL: Source0:

BuildRequires: emacs Requires:      emacs-filesystem >= %{_emacs_version}

BuildRequires: xemacs Requires:      xemacs-filesystem >= %{_xemacs_version}

%description Foo is a package wghich contains auxilliary Emacs and XEmacs support files

%prep %setup -q

%build

%install

%post

%preun

%files %doc %{_emacs_sitelispdir}/foo %{_emacs_sitestartdir}/*.el

%{_xemacs_sitelispdir}/foo %{_xemacs_sitestartdir}/*.el

%changelog

Principles behind the guidelines
The existence of the GNU Emacs and XEmacs variants makes packaging Emacs add-on packaging slightly complex. GNU Emacs and XEmacs have different philosophies regarding add-on packages.

XEmacs has its own packaging system and maintains and distributes its own library of third party add-on modules. These are distributed in Fedora in the xemacs-packages-base and xemacs-packages-extra packages. GNU Emacs doesn't have any equivalent system, and third party add-ons are left for the user or distribution to install.

The packaging naming guidelines state that:

''Packages of emacs add-on components (code that adds additional functionality to emacs compatible editors) have their own naming scheme. It is often the case that a component will add functionality to several different compatible editors, such as GNU Emacs and XEmacs (and possibly development versions of these editors). The package name should take into account the upstream name of the emacs component.''

''Where a component adds functionality to more than one emacs compatible editor, the package name should be of the form emacs-common-$NAME. In this case, the main package should contain only files common to all emacs compatible editors, and the code specific to each should be placed in a subpackage reflecting the specific editor $EDITOR-$NAME eg. xemacs-$NAME, emacs-$NAME (the latter being the package specific to GNU Emacs). An example of this scheme can be found in the package emacs-common-muse.''

''Where a component is designed to add functionality to only a single emacs compatible editor, the main package name should reflect this by being called $EDITOR-$NAME. An example of this situation can be found in the package emacs-auctex, which is built only for GNU Emacs.''

Wherever possible, we encourage making an add-on package available for both GNU Emacs and XEmacs. One common case where that is not desireable is when an add-on package is already available for XEmacs in either xemacs-packages-base or xemacs-packages-extra. For example VM (a mail reader for Emacs) is provided for XEmacs in the xemacs-packages-extra package, but is not included in the emacs or emacs-common packages. Therefore it is sensible to create a package called emacs-vm which is the VM package for GNU Emacs only. Another such example is AUCTeX.

GNU Emacs
For GNU Emacs, files for add-on package foo should be placed in %{_emacs_sitelispdir}/foo which evaluates to /usr/share/emacs/site-lisp/foo.

Usually an add-on package will require a startup file, and this should be called foo-init.el and be placed in %{_emacs_sitestartdir} which evaluates to /usr/share/emacs/site-lisp/site-start.d/.

XEmacs
XEmacs expects add-on packages to be installed under %{_xemacs_sitepkgdir} which evaluates to /usr/share/xemacs/site-packages.

Lisp files for add-on package foo should be placed in %{_xemacs_sitelispdir}/foo which evaluates to %{_xemacs_sitepkgdir}/lisp/foo.

Other files for the add-on which are not elisp files should be placed in package specific sub-directories under %{_xemacs_sitepkgdir} eg. %{_xemacs_sitepkgdir}/etc/foo.

Usually an add-on package will require a startup file, and this should be called foo-init.el and be placed in %{_xemacs_sitestartdir} which evaluates to /usr/share/xemacs/site-packages/lisp/site-start.d/.

Packaging of source elisp files
Typically, an Emacs add-on package will be compiled from source elisp files. The resulting compiled elisp files will then be included in the relevant emacs-foo and xemacs-foo packages. It is important to also include the source elisp files for several reasons. For example when debugging a problem with an (X)Emacs package, the Elisp debugger can look up the relevant code or symbol definition in the source lisp file if present. Also, it's sometimes helpful to jump to a variable description string from the Emacs help system.

BuildArch for (X)Emacs add-on packages
You should set BuildArch: noarch for add-on packages which only compile elisp files during building.

If the package building process also compiles programs in other languages, you may need to not set BuildArch.

Requires for GNU Emacs and XEmacs
Add-on packages should have appropriate Requires entries for the flavour of (X)Emacs they are targeted at. Both GNU Emacs and XEmacs are available in two different packages - some details of these packages follow.

1. GNU Emacs is packaged as two variants. The emacs package is built with Xorg support to allow the user to run Emacs in a windowed environment. The emacs-nox package is built without Xorg support and hence allows Emacs to be run only in a console. Note:
 * Both the emacs and emacs-nox packages have Requires: emacs-common.
 * Both emacs and emacs-nox have a virtual Provides: emacs(bin)

2. XEmacs is packaged as two variants. The xemacs package is built with Xorg support to allow the user to run Emacs in a windowed environment. The xemacs-nox package is built without Xorg support and hence allows Emacs to be run only in a console. Note:
 * Both the xemacs and xemacs-nox packages have Requires: xemacs-common.
 * Both xemacs and xemacs-nox have a virtual Provides: xemacs(bin)

Assuming your add-on package will work in both a windowed and a console (X)Emacs session, it is wrong to have Requires: emacs or Requires: xemacs as that would pull in a dependency on Xorg even if the console variants of (X)Emacs was installed. Rather you should use Requires: xemacs(bin) for XEmacs add-on packages, and Requires: emacs(bin) for GNU Emacs add-on packages.

If the package ONLY works with Xorg support built into (X)Emacs, then the packages should have Requires: emacs or Requires: xemacs. This is very uncommon.

Why we need versioned Requires
Many elisp packages aim for backwards source level compatibility by checking whether some features exist in the (X)Emacs in use when the package is being run or byte-compiled. If yes, they use what's available. If no, they provide their own versions of missing functions, macros etc. This propagates into *.elc during byte compilation, and quite a few functions do get added between upstream (X)Emacs releases.

So let's say I byte-compile a package into *.elc with XEmacs 21.5.28. Elisp package quux checks if the foo-bar function is available in the XEmacs being used to byte-compile it. Yes, it is, so the internal backwards compat version of foo-bar included in quux does not end up in the *.elc. Now, let's assume foo-bar was added in XEmacs 21.5.28 and didn't exist in 21.5.27 and we're trying to run the *.elc with 21.5.27 -> boom, foo-bar is not available. Note: this wouldn't happen if only *.el were shipped - *.elc are the potential and likely problem. Requiring >= version of the (X)Emacs used to byte-compile the *.elc is not the only solution (nor enough for all corner cases), but is the best one we currently have available.

The main package and subpackages will need to have appropriately version Requires to ensure that a recent enough version of (X)Emacs is installed. (X)Emacs byte compiled lisp is usually forward compatible with later (X)Emacs versions, but is frequently not compatible with earlier versions of (X)Emacs.

Determining the Required (X)Emacs version at package build time
It is recommended to derive greater-than-or-equal-to valued versioned dependencies from the version of (X)Emacs used to byte-compile the package at package build time. The emacs-common and xemacs-common packages both place files in /etc/rpm which define macros containing the version of (X)Emacs installed. The relevant macros are:

%{_emacs_version} %{_xemacs_version}

Other packages containing Emacsen add-ons (Case II)
It is often the case that a software package, while not being primarily an Emacs add-on package, will contain components for (X)Emacs. For example, the Gnuplot program contains some elisp files for editing Gnuplot input files in GNU Emacs and running Gnuplot from GNU Emacs. In this case, we want to enable the (X)Emacs support IF (X)Emacs is installed, but we don't want to mandate the installation of (X)Emacs on installation of this package since (X)Emacs is not required for providing the core functionality of the package. To enable this, the emacs-filesystem and xemacs-filesystem sub-packages were created which own the /usr/share/emacs/site-lisp and /usr/share/xmeacs/site-packages directories respectively. A package can then Require these (x)emacsfilesystem packages in order to install their Elisp files without pulling in (X)Emacs and their dependency chain.