Simon Josefsson [29/May 8:49am +02] wrote: > diff --git a/copyright-format-1.0.xml b/copyright-format-1.0.xml > index 954a65b..a5a7aa0 100644 > --- a/copyright-format-1.0.xml > +++ b/copyright-format-1.0.xml > @@ -246,6 +246,11 @@ > <link linkend="copyright-field">Copyright</link>: optional. > </para> > </listitem> > + <listitem> > + <para> > + <link linkend="files-excluded-included-field">Files-Excluded, > Files-Excluded-*, Files-Included, Files-Included-*</link>: optional. > + </para> > + </listitem> > </itemizedlist> > <para> > The <varname>Copyright</varname> and <varname>License</varname> > @@ -498,6 +503,27 @@ License: MPL-1.1 > </para> > </section> > > + <section id="files-excluded-included-field"> > + <title><varname>Files-Excluded, Files-Excluded-*, Files-Included, > Files-Included-*</varname></title> > + <para> > + <link linkend="white-space-lists"> > + Whitespace‑separated filename patterns</link>, as in the > + <link linkend="files-field">Files</link> field (including > + wildcards and directory names), used to indicate which parts > + of the upstream source specified in the Source field will > + not be included in the Debian source package. Files‑Excluded > + lists patterns for files or directories to > + omit. Files‑Included lists patterns for files that should > + not be omitted even if they match a Files‑Excluded rule. For > + multi‑orig.tar sources, Files‑Excluded‑COMPONENT and > + Files‑Included‑COMPONENT apply the same logic but only to > + the specified orig.tar component. These fields may also be > + used by maintainer tools to perform the exclusions, but such > + tools should not require the machine-readable > + debian/copyright file format for correct operation. > + </para> > + </section> > + > <section id="license-field"> > <title><varname>License</varname></title> > <para>
Seconded, thanks. -- Sean Whitton
