Bug#685506: debian-policy: Please add field Files-Excluded to machine readable copyright files definition
Hi,
Am Thu, Jan 27, 2022 at 02:52:18PM -0700 schrieb Sean Whitton:
>
> We don't remove files for the sole reason that they're intended for use
> on other platforms. It's typically only done if the files are huge. So
> please remove this one from the list.
>
> How about just saying: we always remove non-DFSG files if the package is
> intended for main or contrib, and sometimes there are other files that
> are removed for technical reasons or because they are both unneeded and
> very large, and both these sorts of removal are documented using this
> field?
I like this wording. I'm not sure whether we might add what I'm doing
in practice: If there is the need to remove non-DFSG files it might
make sense to use other files that are typically unused for Debian and
thus are just bluring the content of the tarball.
I'm unsure whether we should really add this to policy but this is what
I'm doing.
> > + <para>
> > + These types of files, or any others that Debian does not want to
> > + include in our archive, must be stripped from the upstream tarball
> > + prior to uploading. The <varname>Files-Excluded</varname> field serves
>
> How about "are stripped" not "must be stripped", as the normative stuff
> is explained more precisely over in the Policy manual itself?
+1
> > + to document the removal of these files from the original upstream
> > + source. This allows others to understand or audit how the source
> > + distribution in Debian is derived from the upstream source.
> > + </para>
> > + <para>
> > + Additionally, once documented in this manner, various tools such as
> > + <literal>uscan</literal> or <literal>mk-origtargz</literal> can use
> > + this information as instructions on how to automatically repack an
> > + upstream source distribution into one suitable for use within Debian.
>
> Nice.
Thanks a lot for working on this in Debian policy
Andreas.
--
http://fam-tille.de
Reply to: