Re: Enabling uscan to simply remove files from upstream source
- To: email@example.com
- Subject: Re: Enabling uscan to simply remove files from upstream source
- From: Jon Dowland <firstname.lastname@example.org>
- Date: Fri, 7 Sep 2012 13:54:31 +0100
- Message-id: <20120907125431.GC4705@debian>
- Mail-followup-to: email@example.com
- In-reply-to: <20120825081857.GB3847@falafel.plessy.net>
- References: <20120821102121.GD14977@an3as.eu> <CAKTje6HhD392gEPadjMXkQE3VFG5J++qG1fKdRQn4sjF9bz3cw@mail.gmail.com> <20120822080938.GG8759@jones.dk> <20120825040303.GE2450@falafel.plessy.net> <20120825052406.GC21988@an3as.eu> <20120825081857.GB3847@falafel.plessy.net>
On Sat, Aug 25, 2012 at 05:18:57PM +0900, Charles Plessy wrote:
> I also considered, but the information of what files are excluded when creating
> the Debian source package is not relevant to upstream.
> More simply, I think that if debian/watch would radically change its format to
> YAML or the Debian control data file syntax, it would be a good place for the
> Files-Excluded field.
The copyright file is, as the name suggests, for copyright information.
The watch file is, as the name suggests, for watching for upstream releases.
Can we please just have a new file for a new purpose, rather than overloading
ones that are succinct, single-purpose and consistent?
We can then pick a syntax that fits the problem, rathen than trying to bend and
contort one that doesn't.