On 2020-04-19 15:39+0000, Scott Kitterman wrote:
As a member of the FTP Team, I see this situation from time to time.  It's 
usually not a serious problem, but I agree with Zigo on this.

Where it becomes problematic is when code in debian/ becomes intermingled with 
the installed upstream code.  One has to look at the license of both upstream 
and debian/ to determine the effective license of the package.  If the licenses 
are incompatible, then the binary isn't distributable.  I have seen this happen.

Aligning the license of the packaging with the upstream license makes it all 
much simpler.

...

OK, it makes sense. Thanks for the rationale!

If you intend to maintain this package in DPMT or PAPT, we have a standard 
gbp.conf for the teams that doesn't include this, so it would be inappropriate. 
 In any case, it's the default for a format 3.0(Quilt) source package, so 
there's no need for it anyway:

https://manpages.debian.org/testing/git-buildpackage/gbp-import-orig.1.en.html

Scott K

OK. I removed the setting.

--
Félix

Attachment: signature.asc
Description: PGP signature

Reply via email to