On Wed, Sep 10, 2014 at 12:48 AM, Andrey Rahmatullin wrote:
another clear benefit is reduced package cruft.
The only thing that is reduced is the size of the orig tarball.
People do actually do review package source changes (think every
release team unblock, security analysis, etc.), and the
Quoting Russ Allbery (2014-09-10 06:38:21)
Osamu Aoki os...@debian.org writes:
It may be good to have a set of specifically defined file types for
exclusion in DEP-5 policy. Then we can skip listing them in the
copyright file. The helper script can generate a template for the
copyright
On Wed, Sep 10, 2014 at 10:01:42AM +0200, Jonas Smedegaard wrote:
How about - instead of codifying into Polict that some licensing is ok
to ignore (which sounds very wrong to me) we instead recognize that some
pattern of files are very commonly the same across packages: Add a DEP-5
snippet
Hi,
On Wed, Sep 10, 2014 at 10:20:06AM +0200, Stefano Zacchiroli wrote:
How about using your snippet to improve our packaging work-flows
instead? For instance, we can have a lintian check that verifies if
those files are present in the source package and emit a warning if they
are not listed
Hi here is an example:
On Wed, Sep 10, 2014 at 11:48:38PM +0900, Osamu Aoki wrote:
...
$ debmake -k
...
=== debian/copyright checked for 90 data ===
Pattern #00: *
File: data/symbol.txt
- GPL-2+
+ BSD-3-Clause
Pattern #00: *
File: depcomp
config.sub
m4/intltool.m4
5 matches
Mail list logo
