1663
Comment: Rename as we put it in d/control nowadays
|
1713
add link to tips page
|
Deletions are marked like this. | Additions are marked like this. |
Line 35: | Line 35: |
== Subpages == * [[EmacsenTeam/Tips|Tips]] |
Debian Emacsen team
Contact
- #debian-emacs on irc.debian.org
Scope
- Emacs Lisp addon packages
- GNU Emacs backports
i.e. does not (yet) include any main archive Emacsen themselves.
Membership
Defined by our salsa group (not (yet) by tracker.debian.org).
Addons packaging policy
All binary packages installing into site-lisp/elpa (in particular all packages using dh_elpa) should be named elpa-foo where foo is the ELPA package name.
+ Note that this is often different to the upstream repository name. E.g. elpa-f is called 'f.el' by upstream.
- Source package names are upstream project names. Prefix 'emacs-' or suffix '-el' if and only if that name is too generic.
- We use one git repository for each upstream package.
- We keep the upstream source in the packaging git repository.
- Versions should be based on those used by the upstream author, not e.g. MELPA
- + Though if there is a discrepancy, try to get it resolved with upstream before uploading.
- Maintainer field should be
Debian Emacsen team <debian-emacsen@lists.debian.org>
We generally expect to be able to work on packages as a team
See elpa-hello for sample debian/* files snippets that use dh_elpa and follow policy.
Subpages
Useful links
Old team wiki content (not yet fully migrated to here)