Charles Plessy <ple...@debian.org> writes:
> Le Tue, Aug 21, 2012 at 03:48:33PM +0200, Andrew Shadura a écrit :

>> By the way, how about adding something under debian/source/... to allow
>> automatic repacking regardless of Files-Excluded? (Or please tell me
>> how to repack upstream's zipball to targz automatically without having
>> to specify --repack every time.)

> actually, wouldn't a file under debian/source (or directly under
> debian/) be a better place than debian/copyright, given that there are
> reason for excluding files that are not related to copyright, such as
> for their size, or a safeguard against accidentally building against
> convenience code copies.

It would be nice to keep all of the information about the provenance of
the upstream source in one location.  Currently, that's (mostly)
debian/copyright.  If we start moving that data, perhaps we could move
*all* of it, rather than deciding every new piece of data piecemeal?

The argument for having that data in debian/copyright is, so far as I
understand it, two-fold: identifying the upstream location allows people
to review and confirm license information, and some upstream licenses may
require pointers to the original source location.  However, the latter
should, I hope, be dealt with by the license text, which we have to
reproduce anyway, and in any case are a minority.  And the former seems
like a relatively weak association with debian/copyright to me.

Personally, I care more about it being in one place than about what that
place is.  As long as people aren't going to move this information out of
debian/copyright, I want new, related information, such as excluded files,
to go in the same place so that the information isn't split.  But I'm fine
with moving it entirely.

-- 
Russ Allbery (r...@debian.org)               <http://www.eyrie.org/~eagle/>


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87lih7n9y3....@windlord.stanford.edu

Reply via email to