Differences between revisions 1 and 2
Revision 1 as of 2018-07-15 00:19:42
Size: 1453
Comment:
Revision 2 as of 2018-07-15 00:21:52
Size: 1481
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
Many unelpafied packages packages have extra "sugar" configuration such as adding autoload cookies that activate ''mode'' for '''REGEX'''. David Bremner and I discussed this on #debian-emacs and he suggested debian/debian-autoloads.el. At this stage it's unclear whether this should be a suggested or recommended priority. Many unelpafied packages packages have extra "sugar" configuration such as adding autoload cookies that activate ''mode'' for '''REGEX'''. David Bremner and I discussed this on #debian-emacs and he suggested debian/debian-autoloads.el [for Emacsen Team packages]. At this stage it's unclear whether this should be a suggested or recommended priority.

Translation(s): none


Proposals for Discussion or Sprints at DebConf18

Standardised location for Debian-specific configuration in src:packages

Many unelpafied packages packages have extra "sugar" configuration such as adding autoload cookies that activate mode for REGEX. David Bremner and I discussed this on #debian-emacs and he suggested debian/debian-autoloads.el [for Emacsen Team packages]. At this stage it's unclear whether this should be a suggested or recommended priority.

Another case: packages that need to have a variable set in order to work properly on Debian. eg: php-mode needs the location of a local copy of documentation to avoid querying php.net and Elpy will need the python interpreter to be set to /usr/bin/python3 when we drop Python 2—at the latest.

Bremner advocates storing this in an autoloads file rather than maintaining a patch against upstream sources, and also proposes debian/debian-autoloads.el as the standardised location. I'll second that motion, and will also support an alternative name if debian/debian-autoloads.el is not preferred for some reason.