From 608f05bf99158c87106fd4b21a11fab056b8cf5a Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Sat, 6 Oct 2018 11:17:56 -0700 Subject: rewrite docs for foo.elpa --- dh_elpa.in | 22 +++++++++++++--------- 1 file changed, 13 insertions(+), 9 deletions(-) diff --git a/dh_elpa.in b/dh_elpa.in index 652dfda..3376612 100755 --- a/dh_elpa.in +++ b/dh_elpa.in @@ -39,15 +39,19 @@ detailed in dh_elpa_test(1). List of files to be installed into I (respectively into the first binary package) as an elpa package. The format is a set of -lines, where each line lists a file or files to install, and at the -end of the line tells the subdirectory it should be installed in. You -may use wildcards in the names of the files to install. - -If you list exactly one filename or wildcard-pattern on a line by -itself, with no explicit destination, then B will install the -file into the top level elpa package directory. Only elisp files in -the top level elpa package directory will be automatically -byte-compiled. +lines, where each line is either (i) a single filename or glob, or +(ii) a space-separated list of one or more filenames or globs, +followed by the name of a destination subdirectory (which should not +begin with a slash). + +For lines with a single file or glob, B will install matching +file(s) into the top level elpa package directory. + +For lines which include a destination subdirectory, B will +install matching file(s) into the named subdirectory. + +Only elisp files in the top level elpa package directory will be +automatically byte-compiled. =item I-pkg.el -- cgit v1.2.3