Re: [Pkg-dns-devel] Bug#833309: "Browserified" stuff (knot-resolver-module-http: please package embedded epoch.js separately)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Oct 12, 2016 at 10:09:12PM +0200, Martín Ferrari wrote:
> On 12/10/16 21:41, Vincent Bernat wrote:
> >> I don't think that shipping a binary compiled upstream should be
> >> allowed, so where's the line drawn?
Technically it would be allowed, but because it is pretty much impossible to
prove that the binary was indeed compiled with a compiler in Debian and from
the provided source, it is probably rejected unless the packager has a good
reason for doing it this way.
By the way, that isn't impossible: xburst-tools contains a boot loader for a
mips device, which is included as binary in the package. On everything except
mips a cross compiler would be required to build it. Those haven't been in
Debian for a long time (but I think they are now), so shipping a binary that
could only be rebuilt on mips is acceptable in such a case. But note that the
compiler _is_ in Debian; it may just not be usable on every arch.
> > Dunno. It would be great if the line wasn't challenged just to prove a
> > point and eject a lot of packages from main while DFSG#2 is correctly
> > met.
>
> It is really not in my plans to challenge that line. It is just that I
> would like to understand the rules properly.
It's not about DFSG#2. Packages in contrib _do_ meet the entire DFSG, but
require or recommend a non-free component for some major functionality. We
require packages to be buildable from source, so if they require packages
outside of main for that, they cannot be in main themselves.
Thanks,
Bas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJX/qM6AAoJEJzRfVgHwHE6mA8P+gNPxycBMWPKCgV7N+hHSB60
2J+HDvLG40d4+YL7japyWIzovY7senVobl5Dz4IfjEqJovbkgprXLRxK3OqTn2EQ
pOk9ca2MM8IpYCvOGPfPVulDt2JYgalcj76kxYIzrIJnTAuylvohrz2R0kFIG4sQ
IkhSJxhOj4MlocRMrS6tWSDnJ6BbvXZRFiLtYdwEax4Hm/EsJHQlFkTZqJemetZ+
sQ/OKOC21Cv9HNC1I9Om4oKJnxX06yb1VGxWLP5qCZk8/skwZurJlG4LqnCzf5/H
cKTQeVnalWFo3HuFmFOAfZPeFMxmfIrK91vCkzynFKapqz3tN7yMilFk0Asr8bfH
Gjvq6q2SBoKUl2HPgm9de33TOUPkDsM9jQJz/JeDUpY2uwUsqqZHphIJvW0VsdfB
UCfaSlRpTgvh8axjVW3hWvKaQ1dgLwctedcIWRDzgdndFm8dYhKQOHimVVyVXji4
C8xZYoCGC32sODhW8slBBypx/3jBMN5XOUSCRN1lPzS6A/PERckFp7XQFG8sp4Qs
VFE80QUBRigW0XXgmzSvWozrUf492FnVXBOb/t1YDNptTNDiGeUJl6d+yn6FVF6m
k/aDJv5Epxi0IIhvXrXUEjTMeQxtMed6xl+jjfVO0dVGpf/y094SkOjSOoQRLRvi
dFNMwAFWlQhfv7SsBVhl
=Lk3u
-----END PGP SIGNATURE-----
Reply to: