Am Samstag, den 19.03.2011, 19:43 +0000 schrieb Arand Nash:
> Initial report is somewhat erroneous, some of this is detailed in 
> README.Debian, items in include/ are not in the binary package.
> However, they are still in the dfsg.orig.tar.gz, which I assume is a 
> problem.
It's not a problem as long as they are DFSG-compliant. I once read
somewhere in the maintainer guide, that we should only remove non-DFSG
stuff from .orig.tar.gz files as Debian users should be expected to
build/compile software for different platforms from our .orig.tar.gz
sources.
I was searching the maintainers' guide for the exact wording, but failed
to find it, so I can't give evidence here (d'oh!). Honestly I don't
think there are many users out there who really use our .orig.tar.gz
files to compile software for any *BSD or whatever ;)

> (./include/wincompat.h is "all rights reserved" hence impossible to 
> distribute, no?).
Uhm, there you're right. I think I remove that file (and others, if
there are more) and do a $VERSION-repack.dfsg upload with full sources.
Any objections?

> Also, the additional ./enet/ items are not mentioned in the 
> README.Debian nor in the copyright
That's not true (phew! ;) ) it's mentioned at the end of
debian/copyright.

> It seems like the package builds fine with the include/ directory 
> removed, why is it in the dfsg tarball?
Oops, I already answered that above.

Greetings - Fuddl

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to